home *** CD-ROM | disk | FTP | other *** search
Text File | 1992-11-11 | 153.1 KB | 4,616 lines |
-
-
- ╔══════════════════════════════════════╗
- ║ ║
- ║ pEDIT PLUS ║
- ║ ──────────────────────── ║
- ║ the personal EDITor PLUS ║
- ║ ║
- ║ ║
- ║ Version 1.1 ║
- ║ ║
- ║ ║
- ║ November 15, 1992 ║
- ║ ║
- ╚══════════════════════════════════════╝
-
-
-
-
-
-
- pEDIT COPYRIGHT 1989 - 1992
-
-
-
- _______
- ____|__ | (R)
- --| | |-------------------
- | ____|__ | Association of
- | | |_| Shareware
- |__| o | Professionals
- -----| | |---------------------
- |___|___| MEMBER
-
-
-
-
-
-
-
-
-
-
-
-
-
- T. G. Muench
- P.O. Box 11536
- Prescott, AZ 86304-1536
- (602) 445-2479
-
- CIS 71171,2424
-
-
-
-
-
-
-
-
-
-
-
-
-
-
-
-
- This program is produced by a member of the Association of Share-
- ware Professionals (ASP). The ASP wants to make sure that the
- shareware principle works for you. If you are unable to resolve a
- shareware-related problem with an ASP member by contacting the
- member directly, ASP may be able to help.
-
- The ASP Ombudsman can help you resolve a dispute or problem with
- an ASP member, but does not provide technical support for members'
- products. Please write to the ASP Ombudsman at 545 Grover Road,
- Muskegon MI 49442 or send a CompuServe message via CompuServe Mail
- to ASP Ombudsman [70007,3536].
-
- The OMB may also be contacted by FAX, by sending to the ASP FAX
- number: (617) 788-2765. In communicating with the OMB, please in-
- clude a telephone and/or FAX number if available.
-
-
-
-
-
-
- DISCLAIMER OF WARRANTY
-
-
- THIS SOFTWARE IS SUPPLIED AS IS. THE AUTHOR DISCLAIMS ALL
- WARRANTIES, EXPRESSED OR IMPLIED, INCLUDING, WITHOUT
- LIMITATION, THE WARRANTIES OF MERCHANTABILITY AND OF FITNESS
- FOR ANY PURPOSE. THE AUTHOR ASSUMES NO LIABILITY FOR
- DAMAGES, DIRECT OR CONSEQUENTIAL, WHICH MAY RESULT FROM THE
- USE OF THIS SOFTWARE.
-
-
-
- THIS IS A FULLY FUNCTIONING PROGRAM. IT IS NOT A DEMO NOR IS
- IT CRIPPLED IN ANY WAY. ALL FEATURES ARE DOCUMENTED IN THE
- ON-DISK MANUAL. IF YOU HAVE TROUBLE USING THE PROGRAM OR
- FEEL YOU DID NOT RECEIVE ALL THE FILES, CONTACT THE AUTHOR
- FOR ASSISTANCE.
-
-
-
-
- A C K N O W L E D G E M E N T S
-
-
- The Author wishes to thank:
-
- Jim Hass of MicroFox Company, author of the superb DOS shell HDM-
- IV. Jim has had the foresight to see the potential of pEDIT by
- building support for it into HDM. He has also helped with testing
- and has made many suggestions to make pEDIT the best it can be.
-
- Thomas G. Hanlin III, author of many assembly language libraries
- for BASIC. The graphical pEDIT would not have been possible
- without his GrafWiz routines which provide superfast text display
- in graphics modes. These routines are now included in his BasWiz
- library.
-
-
- C O N V E N T I O N S
-
-
- The following conventions are used throughout this documentation
- and in the tutorial.
-
- pEDIT commands are shown in upper case; examples are RULER and
- TRIM BUFFER. Command parameters are shown in lower case with a
- vertical bar (|) separating options; an example is "SET VIDEO
- text|graphics".
-
- Keyboard key, ButtonBar button and mouse button names are all
- enclosed in angle brackets. For labelled keys, the key name cor-
- responds to what is stamped on the key; examples are <Home> and
- <PgDn>. An exception is the "5" key on the keypad, which is named
- <Center>. The arrow keys have the names <Left>, <Right>, <Up> and
- <Down>.
-
- Shift, Control and Alt keys are prefixed by Shift-, Ctrl-and Alt-,
- respectively. The Function keys are named <F01> through <F12>.
- Some older keyboards do not have the <F11> and <F12> keys. Control
- keys are sometimes shown as ^X for <Ctrl-X>.
-
- ButtonBar buttons are referenced by their 3-character text mode
- abbreviations as shown in Fig. 3; examples are <CMD>, <FND> and
- <CUT>.
-
- The mouse button names are <MLB> and <MRB> for the left and right
- buttons, respectively. pEDIT PLUS fully supports a Microsoft
- compatible 2-button mouse; the middle button of a 3-button mouse
- is ignored.
-
-
-
-
- T A B L E O F C O N T E N T S
-
-
-
- Introduction . . . . . . . . . . . . . . . . . . . . . 1
-
- Installing pEDIT PLUS
-
- 1. General Information . . . . . . . . . . . . . . 3
- 2. Floppy Disk Installation . . . . . . . . . . . 5
- 3. Hard Disk Installation . . . . . . . . . . . . 6
-
- Quick Starting pEDIT PLUS
-
- 1. Overview . . . . . . . . . . . . . . . . . . . 8
- 2. Command Mode . . . . . . . . . . . . . . . . . 12
- 3. Prompting Mode . . . . . . . . . . . . . . . . 12
- 4. The ButtonBar . . . . . . . . . . . . . . . . . 13
- 5. Using a Mouse . . . . . . . . . . . . . . . . . 15
-
- pEDIT PLUS Commands
-
- 1. Cursor Movement . . . . . . . . . . . . . . . . 17
- 2. Text Manipulation . . . . . . . . . . . . . . . 19
- 3. Text Deletion . . . . . . . . . . . . . . . . . 22
- 4. Searching . . . . . . . . . . . . . . . . . . . 23
- 5. Files . . . . . . . . . . . . . . . . . . . . . 25
- 6. Buffers . . . . . . . . . . . . . . . . . . . . 27
- 7. Windows . . . . . . . . . . . . . . . . . . . . 29
- 8. Cut and Paste . . . . . . . . . . . . . . . . . 31
- 9. Key Macros . . . . . . . . . . . . . . . . . . 33
- 10. Miscellaneous . . . . . . . . . . . . . . . . . 35
-
- Macro Facility
-
- 1. Macro Types . . . . . . . . . . . . . . . . . . 41
- 2. Macro Execution . . . . . . . . . . . . . . . . 41
- 3. Sample Macros . . . . . . . . . . . . . . . . . 41
- 4. Converting Disk Macros . . . . . . . . . . . . 42
-
- Defining Keys in pEDIT PLUS . . . . . . . . . . . . . 43
-
- Extended DOS Shell . . . . . . . . . . . . . . . . . . 44
-
- Drawing With pEDIT PLUS . . . . . . . . . . . . . . . 45
-
- Printing From pEDIT PLUS . . . . . . . . . . . . . . . 46
-
- Compiling From pEDIT PLUS
-
- 1. Manual Invocation . . . . . . . . . . . . . . . 48
- 2. Batch File . . . . . . . . . . . . . . . . . . 48
- 3. Disk Macros . . . . . . . . . . . . . . . . . . 48
-
-
-
-
-
- Error Handling
-
- 1. Insufficient Internal Storage . . . . . . . . . 50
- 2. Insufficient Disk Space . . . . . . . . . . . . 50
- 3. No Initialization File . . . . . . . . . . . . 50
-
- Miscellaneous/Legalities
-
- 1. Copyright Notice . . . . . . . . . . . . . . . 51
- 2. Registration . . . . . . . . . . . . . . . . . 51
-
- Appendices
-
- A. Key Bindings
- 1. Labelled Keys . . . . . . . . . . . . . . . 52
- 2. Standard . . . . . . . . . . . . . . . . . . 53
- 3. WordStar . . . . . . . . . . . . . . . . . . 55
- 4. WordPerfect . . . . . . . . . . . . . . . . 57
- 5. Microsoft Quick . . . . . . . . . . . . . . 59
- 6. Emacs . . . . . . . . . . . . . . . . . . . 61
- B. The DOS Environment . . . . . . . . . . . . . . 63
- C. Supported Video Displays . . . . . . . . . . . 64
- D. Initialization File . . . . . . . . . . . . . . 66
- E. Help Files . . . . . . . . . . . . . . . . . . 67
- F. Color Codes . . . . . . . . . . . . . . . . . . 68
- G. Troubleshooting . . . . . . . . . . . . . . . . 69
- H. RAMEDIT . . . . . . . . . . . . . . . . . . . . 72
-
-
-
-
- I N T R O D U C T I O N
-
-
- pEDIT PLUS is a DOS-based text editor with a graphical user
- interface for the IBM Personal Computer. The program is referred
- to interchangably as pEDIT PLUS, pEDIT+, and pEDIT. The program
- has has been tested with MDA (monochrome text), HGA (Hercules
- monochrome in text mode), CGA, EGA and VGA displays. pEDIT PLUS
- requires PC/MS-DOS 2.1 or higher, 384k of memory and 720k of
- floppy drive capacity; 512k memory is recommended as is a hard
- disk.
-
- This second release of pEDIT PLUS retains the graphical Button-
- Bar interface and mouse support of its predecessor. The ButtonBar
- has 18 colorful "buttons" that provide fast access to the most
- common editing functions. The philosophy behind the ButtonBar is
- simple: it's easier to press a button than pull down a menu.
-
- pEDIT will handle standard ASCII text files with lines up to
- 32000 characters in length terminated by a carriage-return line-
- feed. pEDIT is not a binary editor although it can be used to view
- binary files. pEDIT PLUS is also not a word processor or desktop
- publisher and does not import graphics or support multiple fonts.
- pEDIT does, however, have several features normally associated
- with word processors: settable margins, automatic word wrap, para-
- graph reformat and justification, paragraph indent. Lines can be
- centered or made flush left or right. Words (or parts of words)
- can be Capitalized, lower-cased or UPPER-CASED.
-
- pEDIT+ has other capabilities which make it competitive with ANY
- shareware editor available today: split screen editing; edit up to
- 16 files at one time; on-line topic help; picklists; line and box
- drawing; compile without leaving the editor; and global search and
- replace.
-
- The editor configures itself by loading an 'initialization' file
- at start up. This INI file contains environment settings and key
- bindings that are used to customize the editor. You can make pEDIT
- PLUS work the way you want it to work... even mimic another editor
- such as WordStar, WordPerfect, Microsoft's Quick Editor or Emacs.
- pEDIT+ is completely configurable; if you don't like any of the
- supplied configurations, modify them or create your own.
-
- pEDIT is unique among shareware editors in that everything is
- treated as text in a buffer. Any command can be recalled from a
- Command buffer, edited and reissued. And, the output from shelled
- DOS commands is available in a special DOS buffer.
-
- There is a command line interface for those who want to use it.
- It is primarily intended for commands that are used infrequently.
-
-
-
- - 1 -
-
-
-
- The more efficient method is to use the keyboard and, of course,
- the mouse and ButtonBar.
-
- Every effort has been made to make pEDIT+ perform as efficiently
- as possible. The speed is quite good on an AT (or higher) class
- machine with a hard drive. All text is stored entirely in memory,
- which makes accessing any part of the file very fast. The user can
- move from the top to the bottom of any buffer instantaneously.
-
- Displaying text in graphics mode is normally painfully slow. For
- this reason, pEDIT PLUS uses special assembly language routines
- that bypass the BIOS and write directly to the hardware. However,
- scrolling (which does use the BIOS) is still quite slow when
- compared to text mode. For those who prefer speed to the graphical
- interface, a text mode is available on all displays. Text mode
- uses direct video writes for near instantaneous screen updates.
-
- pEDIT PLUS 1.1 has improved mouse support and the ability to
- define virtually any key on the keyboard. The more standard mouse
- operations include double clicking and true click and drag for
- selecting text. The new keyboard interrupt handler allows for the
- definition of any combination of Shift-, Ctrl- and Alt- keys. A
- sample WordPerfect configuration is now included, and the STD
- (Standard) configuration is now CUA-compliant. CUA, which stands
- for Common User Access, is part of IBM's SAA (Systems Application
- Architecture)--an attempt to standardize the user interface.
-
-
-
-
-
-
-
-
-
-
-
-
-
-
-
-
-
-
-
-
-
-
-
-
-
-
- - 2 -
-
-
-
- I N S T A L L I N G p E D I T P L U S
-
- 1. General Information
-
- The distribution diskette contains the following files. The
- characters XXX in a file name represent one of the 5 supported
- configurations: EMC (Emacs), QUI (Microsoft Quick Editor), STD
- (Standard), WPF (WordPerfect) and WST (WordStar). An asterisk
- indicates the file is included with the registered version only.
-
- READ.ME
-
- Text file containing information about the INSTALL program
- and how to get started with pEDIT
-
- WHATS.NEW
-
- New features of recent releases of pEDIT and pEDIT PLUS
-
- PEDIT.EXE
-
- The pEDIT PLUS executable program
-
- PEDIT.BTN
- PEDIT.HLP
-
- Button and Topic Help files
-
- PEDIT.SHR
-
- File required for internal operation of pEDIT PLUS
-
- PEDITDOC.EXE
-
- Self-extracting file which, when executed, will create
- PEDIT.DOC, the complete pEDIT documentation
-
- PEDITCGA.BAR
- PEDITMGA.BAR
- PEDITEGA.BAR
-
- ButtonBar images for CGA, mono EGA/VGA and color EGA/VGA
-
- TUTORIAL.BAT
- TUTORIAL.DOC
- PRACTICE.TXT
-
- These files are used by the tutorial
-
- PEDITXXX.INI
-
-
-
- - 3 -
-
-
-
- Sample initialization files for Emacs, Microsoft Quick
- Editor, Standard, WordPerfect and WordStar configurations
-
- PEDITXXX.KEY
-
- Keyboard help files to match the above initialization files
-
- XXXLETTR.PM1
- XXXOTHUP.PM1
- XXXOTHDN.PM1
- XXXWREV.PM1
-
- Sample disk macros for each of the supported configurations
-
- REGISTER.DOC
-
- How to register for pEDIT - you can register through Public
- (software) Library or directly from the author; please sup-
- port shareware by registering!
-
- VENDOR.DOC
-
- Information for shareware vendors regarding requirements
- for distributing pEDIT
-
- INSTALL.EXE
-
- Program to install pEDIT PLUS on your system
-
- RAMEDIT.BAT
-
- Sample batch file to copy the auxillary pEDIT files to a RAM
- drive for faster operation
-
- PMCONVRT.EXE
-
- Program to convert PMC macro files to the new PM1 format;
- required to convert any custom macros other than the ones
- supplied with pEDIT
-
- (*)REGISTER.HDM
-
- Explains the benefits of registering the copy of HDM (Hard
- Disk Menu) you'll get when you register pEDIT
-
- (*)KEYRATE.COM
-
- Program to set the keyboard repeat rate on AT and later
- computers
-
- (*)STAYDOWN.COM
-
-
- - 4 -
-
-
-
- Memory-resident utility from PC Magazine to allow Ctrl-, Alt-
- and Shift- commands to be entered as 2 separate keystrokes.
-
- The following installation procedures assume you have a basic
- knowledge of PC operation and can format a diskette. Refer to your
- DOS manual as needed. There are some things to check and decisions
- to make BEFORE starting the installation:
-
- 1. If you are installing pEDIT for the first time, make sure the
- target device has at least 330k of free disk space; allow
- another 155k for the expanded manual
-
- 2. If you are installing over an existing pEDIT, be sure and save
- any customized INI and KEY files by renaming them to other than
- PEDIT.INI and PEDIT.KEY
-
- 3. Choose one of the supplied configurations (Standard, MS Quick,
- WordPerfect, WordStar or Emacs)
-
- 4. If you have a hard drive system, decide if you want INSTALL to
- modify your AUTOEXEC.BAT file to setup the DOS PATH and PEDIT
- environment variable.
-
- 5. Decide if you want to install the optional KEYRATE and STAYDOWN
- utilities (Registered version only).
-
- 6. Decide if you want to print the tutorial documentation and run
- the tutorial.
-
-
- 2. Floppy Disk Installation
-
- This procedure assumes you have 2 floppy drives of at least 360k
- each, or a single 720k (or 1.44MB) drive. In a dual (360k) system,
- Drive A: will hold the program disk with the pEDIT executable,
- initialization and help files. Drive B: will hold a work disk with
- your documents, source programs or other text. In a single (720k
- or 1.44MB) floppy system, everything will fit on one floppy.
-
- The following example is for those with two 360k drives; if you
- have the 3.5" 720k floppy, format just one disk and put everything
- on it.
-
- 1. Format two diskettes; make one (the program disk) a system disk
- if you want to boot from it; label the floppies 'pEDIT PLUS
- Program' and 'pEDIT Work'
-
- 2. Insert the distribution diskette in Drive A:
-
- 3. Set default to the A: drive and run the INSTALL program
-
-
-
- - 5 -
-
-
-
- A>INSTALL<Enter>
-
- 4. Remove the distribution disk from Drive A; move the pEDIT
- Program Disk to Drive A and insert a pEDIT Work Disk in B:
-
- 5. If you want KEYRATE to be run automatically when you boot, copy
- KEYRATE.COM to your system disk and add the following line to
- your AUTOEXEC.BAT file:
-
- KEYRATE FAST
-
- 6. If you want STAYDOWN to be installed when you boot, copy
- STAYDOWN.COM to the system (boot) diskette and add this line to
- AUTOEXEC.BAT:
-
- STAYDOWN
-
- 7. Proceed to "Quick Starting pEDIT PLUS"
-
-
- 3. Hard Disk Installation
-
- This procedure assumes you have one floppy drive and a hard disk
- of any size. You will most certainly want to install pEDIT on the
- hard drive for improved speed.
-
- If you have a hard drive system, two things MUST be set up in
- your AUTOEXEC.BAT file in order for pEDIT to operate properly: (1)
- the directory containing the pEDIT files must be in your DOS PATH;
- (2) the environment variable PEDIT must be defined. If you choose
- not to have the installation program do this for you, you must
- manually edit AUTOEXEC.BAT and make the required modifications. In
- either case, you must reboot for the changes to take effect.
-
- ╔════════════════════════════════╗
- ║ pEDIT PLUS tip: ║
- ║ ║
- ║ If things don't work right ║
- ║ after rebooting, check your ║
- ║ AUTOEXEC.BAT file to make sure ║
- ║ the PATH and SET PEDIT state- ║
- ║ ments are being executed. ║
- ╚════════════════════════════════╝
-
- You will need to decide if you want to install pEDIT in the root
- directory (\), in its own directory (\PEDIT), or in, for example,
- a \TOOLS or \UTIL directory. The example assumes pEDIT will be in-
- stalled from Drive A into its own directory on Drive C.
-
- 1. Insert the distribution diskette in Drive A:
-
-
- - 6 -
-
-
-
- 2. Set default to the A: drive and run the installation program
-
- A>INSTALL<Enter>
-
- 3. Remove the distribution disk from Drive A:
-
- 4. Edit your AUTOEXEC.BAT file if you did not let INSTALL do it
- for you. It must contain the following statements:
-
- PATH=...;C:\PEDIT
- SET PEDIT=C:\PEDIT
-
- 5. If you want KEYRATE to be invoked automatically when you boot,
- copy KEYRATE.COM to the root directory of your hard disk and
- add the following line to AUTOEXEC.BAT:
-
- C:\KEYRATE FAST
-
- 6. If you want STAYDOWN to be installed when you boot, copy
- STAYDOWN.COM to the root directory and add this line to
- AUTOEXEC.BAT:
-
- C:\STAYDOWN
-
- 7. Proceed to "Quick Starting pEDIT PLUS"
-
-
-
-
-
-
-
-
-
-
-
-
-
-
-
-
-
-
-
-
-
-
-
-
-
-
-
-
- - 7 -
-
-
-
- Q U I C K S T A R T I N G p E D I T P L U S
-
- 1. Overview
-
- This section will give you the information you need to get up
- and running with pEDIT PLUS as quickly as possible. The program
- file (PEDIT.EXE) must in a directory contained in your DOS PATH,
- or be in the current directory. The initialization (PEDIT.INI) and
- help (PEDIT.HLP, PEDIT.BTN and PEDIT.KEY) files must be accessible
- via the DOS environment or, again, be in the current directory.
-
- Hard drive users must define a DOS environment variable 'PEDIT'
- so the editor can find the files it needs. The location of the
- pEDIT files will henceforth be referred to as the PEDIT PATH; be
- sure and not confuse this with the DOS PATH.
-
- ╔════════════════════════════════════╗
- ║ pEDIT PLUS tip: ║
- ║ ║
- ║ See the Appendix for a full ║
- ║ discussion of the DOS environment. ║
- ╚════════════════════════════════════╝
-
- If you have a floppy-only system, make sure you have a copy of
- COMMAND.COM (or an alternate command processor) present. This file
- must be available to use the DOS command.
-
- As the following examples show, pEDIT PLUS can be invoked with a
- default or alternate configuration. If @XXX is not included on the
- command line, pEDIT will use the default PEDIT.INI and PEDIT.KEY
- files you selected. If, however, @XXX is specifed, the editor will
- use the files PEDITXXX.INI and PEDITXXX.KEY. XXX represents the
- alternate configuration to be used: EMC (Emacs), QUI (Quick), STD
- (Standard), WPF (WordPerfect) or WST (WordStar) -or one of your
- own.
-
- pEDIT PLUS can be started in one of two ways: with or without a
- file specification. If you have a PEDIT PATH defined, the name of
- the last file you edited--along with the line number and offset--
- are stored in the information file PEDIT.INF. So, to call up the
- last file you were editing, at the DOS prompt enter:
-
- C>PEDIT [@XXX]
-
- The normal way of starting pEDIT would be to specify a file to
- be edited using either a specific or "wildcard" specification:
-
- C>PEDIT [@XXX] D:\PATH\FILENAME.TYP
-
- C>PEDIT [@XXX] D:\PATH\*.DOC
-
-
- - 8 -
-
-
-
-
- ┌──────────────────────────────────────────────────────────┐
- ││ ButtonBar ││
- │├────────────────────────────────────────────────────────┤│
- ││
- ││ ││
- ││ ││
- ││ ││
- ││ ││
- ││ ││
- ││ ││
- ││ ││
- ││ ││
- │├────────────────────────────────────────────────────────┤│
- ││ BufferName Global Mode Direction LLLL:CCCC
- │├────────────────────────────────────────────────────────┤│
- ││ ││
- ││ ││
- ││ ││
- ││ ││
- ││ ││
- ││ ││
- ││ ││
- ││ ││
- ││
- │└────────────────────────────────────────────────────────┘│
- │ BufferName Global Mode Direction LLLL:CCCC │
- └──────────────────────────────────────────────────────────┘
- Command:
- <Message> Working . . .
-
-
-
-
-
-
-
-
-
-
-
- Figure 1
- -----------------
- pEDIT PLUS Screen
-
-
-
-
-
-
-
-
-
- - 9 -
-
-
-
- If you used a wildcard specification, you will be presented with
- a FILES window containing a 'pick list' of all matching filenames
- (unless you see one of the "No matching files" or "Too many files"
- messages).
-
- ╔═════════════════════════════════════╗
- ║ pEDIT PLUS tip: ║
- ║ ║
- ║ "Too many files" means that there ║
- ║ were too many files to list in the ║
- ║ FILES window. Narrow the search by ║
- ║ changing '*.*' to '*.TXT', for ex- ║
- ║ ample. ║
- ╚═════════════════════════════════════╝
-
- Once a file has been selected, the pEDIT signon screen will be
- displayed. This screen will show what initialization file is being
- used - provided, of course, that pEDIT can find one. Lastly, if a
- matching file was found, pEDIT will load that file into the first
- buffer in memory and display the first screenfull of text.
-
- pEDIT uses all 25 screen rows for text, status, commands and
- messages. In text mode, some monitors can display more than the
- standard 25 lines of text: 43 lines on EGA and VGA, and 50 lines
- on VGA. The pEDIT screen can contain 1 or 2 windows. In 25-line
- mode, a single window holds 19 lines of text; if the screen is
- split, each window contains 9 lines.
-
- Figure 1 shows a representation of the pEDIT+ screen with two
- windows displayed. It is important to realize that you can view
- two different files or two portions of the same file when the
- screen is split.
-
- Each window has a status line at the bottom. For a text window,
- the status line shows the buffer name, the current scope (blank =
- Local/Global), mode (Insert/Overstrike) and direction (Forward/-
- Reverse). For an informational window, it indicates the type of
- information being displayed - HELP, FILES, SHOW, LIST, ERROR, etc.
-
- A window can be thought of as a viewport into a portion of the
- text. Figure 2 shows a text buffer (represented by the large box)
- and a window into the text. A window can't show more than 78
- columns of text. pEDIT uses horizontal scrolling so the window can
- be into any portion of the text, not just the leftmost 78 columns.
-
-
-
-
-
-
-
-
-
- - 10 -
-
-
-
- ┌────────────────────────────────────────────────────────┐
- │ │
- │ ┌────────────────┐ │
- │ Now is │the time for all│ good persons to come to the │
- │ aid of │their country. │ │
- │ │ │ │
- │ │<─── Window ───>│ │
- │ │ │ │
- │ └────────────────┘ │
- │ │
- │ │
- │ │
- │ │
- │ │
- │ │
- │ │
- │<─────────────────────── Buffer ───────────────────────>│
- │ │
- │ │
- │ │
- │ │
- │ │
- │ │
- │ │
- │ │
- │ │
- │ │
- │ │
- └────────────────────────────────────────────────────────┘
-
-
-
-
-
-
-
-
- Figure 2
- ---------------
- Buffers/Windows
-
-
-
-
-
-
-
-
-
-
-
-
-
- - 11 -
-
-
-
- The command line displayed at row 24 is actually a one line
- window into the COMMAND buffer. The 'Command: ' prompt is dis-
- played whenever the editor is in command mode.
-
- The message line at row 25 is used to display informational
- text, errors, etc. Also shown at the right margin is the special
- 'Working . . .' message that flashes whenever pEDIT is busy
- loading a file, searching, etc.
-
- Commands are entered either by typing them in at the command
- line, by pressing a defined key, or by 'pressing' a button.
- Obviously, the latter two methods are the most efficient for
- functions you use all the time.
-
- There are some commands you need to know about in this initial
- learning phase. The first is Topic HELP, which is bound to <Shift-
- F01> in the Standard configuration. The second is ALTHELP (for
- alternate or button and keyboard help), which is <F01>. Finally,
- the command LIST KEYS displays a list of all defined keys.
-
-
- 2. Command Mode
-
- You enter Command Mode by pressing the DO COMMAND key or click-
- ing the <CMD> button. The key bound to DO COMMAND depends on the
- configuration you are using but is often the <Esc> key. The prompt
- "Command: " is displayed on the command line and the cursor will
- be positioned after the colon. At this point you can issue any
- valid pEDIT command, for example WRITE FILE or SET MARGINS 10 70.
- If you enter Command Mode without meaning to, simply press <Enter>
- after the prompt to return to editing.
-
- ╔══════════════════════════════════════╗
- ║ pEDIT PLUS tip: ║
- ║ ║
- ║ The Command line is a window into ║
- ║ the COMMAND buffer. All defined keys ║
- ║ work the same as they do in any text ║
- ║ buffer. The mouse cannot be used on ║
- ║ the command line. ║
- ╚══════════════════════════════════════╝
-
-
- 3. Prompting Mode
-
- Prompting Mode is active whenever pEDIT is asking for input and
- the "Command: " prompt is not displayed. In this mode you will not
- have access to all of pEDIT's commands and defined keys. Control
- characters (including tabs) are represented by the Ascii character
- 22 (). Only Insert mode is supported; limited line editing is
- available using a subset of your defined keys:
-
-
- - 12 -
-
-
-
- MOVE UP Recall the last command entered
- ERASE PREV Erase the previous character
- ERASE CHAR Erase current character
- MOVE LEFT Move cursor left one character
- MOVE RIGHT Move right one character
- MOVE HOME Position to start of line
- MOVE END Position cursor to end of line
-
-
- 4. The ButtonBar
-
- The first thing you will notice about pEDIT+ is the graphical
- ButtonBar. The next thing you will notice is that there are no
- menus. As explained in the Introduction, the philosophy behind the
- ButtonBar is this: it is easier to press a button than pull down a
- menu - which can lead to several levels of submenus.
-
- The ButtonBar provides, at the press of a button, 18 of the most
- commonly used editing functions. In graphics mode the buttons will
- be displayed in 2 (CGA), 3 (monochrome EGA/VGA) or 16 (color EGA/-
- VGA) colors. The button will appear to depress when clicked on
- with the mouse. You must click close to the middle of a button as
- pEDIT uses row and column instead of graphics mouse coordinates.
-
- Accessing the ButtonBar without a mouse is clumsy at best. When
- the reserved key <Shift-Esc> is pressed, the text cursor will dis-
- appear and the first (leftmost) button will be "selected". The
- current button is shown in reverse video (text mode) or by depres-
- sing the button (graphics mode). Use the <Left> and <Right> keys
- to select a button; then, press <Enter> to accept the selection or
- ABORT to cancel.
-
- In text mode, the buttons are represented by 3-character abbrevi-
- ations. Figure 3 shows a picture of the ButtonBar in text mode and
- lists the function of each button.
-
-
-
-
-
-
-
-
-
-
-
-
-
-
-
-
-
-
- - 13 -
-
-
-
- ┌┬───┬───┬───┬───┬───┬───┬───┬───┬───┬
- ││ < │HLP│CMD│BUF│INF│GET│WRT│FND│NXT│ /\/
- └┴───┴───┴───┴───┴───┴───┴───┴───┴───┴
-
-
- ┬───┬───┬───┬───┬───┬───┬───┬───┬───┬┐
- \/\ │RPL│DRW│FMT│JST│CUT│PST│DOS│QUI│ > ││
- ┴───┴───┴───┴───┴───┴───┴───┴───┴───┴┘
-
-
-
- < SHIFT LEFT Shift the window left
- HLP HELP Bring up indexed help system
- CMD DO COMMAND Enter command mode
- BUF BUFFER Switch to another buffer
- INF SHOW BUFFER Info about the current buffer
- GET GET FILE Load a file for editing
- WRT WRITE FILE Save modified buffer to disk
- FND FIND Search for text
- NXT FINDNEXT Repeat the last search
- RPL REPLACE Replace text
- DRW DRAW Enter DRAWING MODE
- FMT FILL PARA Reformat paragraph
- JST JUSTIFY PARA Fully justify paragraph
- CUT REMOVE TEXT Cut (to clipboard)
- PST INSERT HERE Paste (from clipboard)
- DOS DOS Shell to DOS
- QUI QUIT Abort the editing session
- > SHIFT RIGHT Shift the window right
-
-
-
-
-
-
-
-
-
-
-
-
-
-
-
-
- Figure 3
- -------------
- The ButtonBar
-
-
-
-
-
- - 14 -
-
-
-
- 5. Using a Mouse
-
- pEDIT PLUS supports a Microsoft compatible 2-button mouse. The
- middle button of a 3-button mouse is ignored. Some mice support a
- proprietary mode in addition to Microsoft; be sure and set your
- rodent up in Microsoft mode. Table 1 summarizes how the mouse is
- used by pEDIT. The right mouse button is currently not used.
-
- The use of a mouse is optional. pEDIT PLUS will detect a mouse
- if one is installed and display a mouse pointer which will move
- across the screen as the mouse is moved across the desktop. The
- pointer appears as a block in text mode and an arrow in graphics
- modes.
-
- ╔══════════════════════════════════════╗
- ║ pEDIT PLUS tip: ║
- ║ ║
- ║ The text cursor and mouse pointer ║
- ║ are not the same! The text cursor ║
- ║ shows where text will be inserted. ║
- ╚══════════════════════════════════════╝
-
- Some mouse terminology should be explained. To "click on" an
- object means to move the mouse pointer to an object on the screen
- and press and release the specified button. To "double click" is
- to press and release the left button twice in rapid succession.
- Finally, to "click and drag" means to hold down the left mouse
- button while dragging (moving) the mouse up, down, left or right.
-
- pEDIT PLUS now supports true "click and drag" to select text.
- Hold down the left button for at least 1/2 second and then "drag"
- the mouse in any direction. Selection will be turned off if you
- click the left button elsewhere in the editing area.
-
- ╔════════════════════════════════════╗
- ║ pEDIT PLUS tip: ║
- ║ ║
- ║ Hold down the left mouse button ║
- ║ to repeat a mouse action such as ║
- ║ clicking on a button or using the ║
- ║ scroll bar. ║
- ╚════════════════════════════════════╝
-
- The Disk Operating System (DOS) stores keystrokes in what is
- called a typeahead buffer and passes them to the application on
- request. Unfortunately, mouse presses are not 'queued' in the same
- way so you can't 'click ahead'. Don't attempt to use the mouse
- when the program is busy and the mouse pointer is turned off.
-
-
-
-
-
- - 15 -
-
-
-
- ┌───────────────┬─────────────────────┬────────────────────┐
- │ Location of │ Function of Left │ Function of Double │
- │ Mouse Pointer │ Button <MLB> │ Clicking <MLB> │
- ╞═══════════════╪═════════════════════╪════════════════════╡
- │ │ │ │
- │ In current │ Move text cursor │ │
- │ text window │ to mouse location │ │
- │ │ │ │
- ├───────────────┼─────────────────────┼────────────────────┤
- │ │ │ │
- │ In other │ Move text cursor │ │
- │ text window │ to other window │ │
- │ │ │ │
- ├───────────────┼─────────────────────┼────────────────────┤
- │ │ │ │
- │ HELP, FILES │ Highlight option │ Select the high- │
- │ or BUFFER │ under the mouse │ lighted option; │
- │ window │ pointer │ same as <Enter> │
- │ │ │ │
- ├───────────────┼─────────────────────┼────────────────────┤
- │ │ │ │
- │ On UpArrow │ Scroll up 1 line │ │
- │ of ScrollBar │ │ │
- │ │ │ │
- ├───────────────┼─────────────────────┼────────────────────┤
- │ │ │ │
- │ On DownArrow │ Scroll down 1 │ │
- │ of ScrollBar │ line │ │
- │ │ │ │
- ├───────────────┼─────────────────────┼────────────────────┤
- │ │ │ │
- │ Between Up- │ Page up to the │ │
- │ Arrow and the │ Previous Screen │ │
- │ DoubleArrow │ │ │
- │ │ │ │
- ├───────────────┼─────────────────────┼────────────────────┤
- │ │ │ │
- │ Between the │ Page down to │ │
- │ DoubleArrow │ the Next Screen │ │
- │ and DownArrow │ │ │
- │ │ │ │
- └───────────────┴─────────────────────┴────────────────────┘
-
-
-
-
- Table 1
- -------------
- Mouse Actions
-
-
-
-
- - 16 -
-
-
-
- p E D I T P L U S C O M M A N D S
-
- This section lists all pEDIT commands. Each command is shown in
- uppercase and has a description following. (B) signifies the com-
- mand is a button on the ButtonBar, (M) means it is accessible with
- a mouse and (R) means it is available in registered versions only.
-
-
- 1. Cursor Movement
-
- Moving the cursor around in the text is among the most basic of
- all editing functions. The following commands are non-destructive;
- that is, the existing text is not modified.
-
- MOVE ABSOLUTE (M)
-
- This function is accessible only with a mouse. When you click the
- <MLB> in the any text window, the text cursor will be moved to the
- location of the mouse pointer.
-
- MOVE TOP
-
- Positions the cursor to the first line of the buffer, scrolling
- or repainting the screen as necessary. pEDIT keeps all text in
- memory, making it very fast to move to the top of the buffer from
- any point in the buffer.
-
- MOVE BOTTOM
-
- Moves the cursor to the dummy last line at the end of the buffer.
- The screen will scroll or repaint as required.
-
- MOVE HOME
-
- The action of MOVE HOME depends on the position of the cursor
- within the current line. If the cursor is not at the beginning of
- a line, it will move there. If it is at the start of a line, it
- will wrap to the start of the previous line. This command is
- normally bound to the <Home> key.
-
- MOVE END
-
- The action of MOVE END depends on the position of the cursor
- within the current line. If the cursor is not at the end of the
- line, it will move there. If it is at the end of a line, it will
- wrap to the end of the next line. Normally bound to the <End> key.
-
- MOVE UP
-
- Moves the cursor up one line in the current buffer. There can be
- no action if the cursor is already on the first line of the
-
-
- - 17 -
-
-
-
- buffer. pEDIT keeps the cursor as close as possible to the same
- column. This command is normally bound to the <Up> key.
-
- MOVE DOWN
-
- Moves the cursor down one line in the current buffer. The cursor
- cannot move if it is already on the dummy last line of the buffer.
- pEDIT keeps the cursor as close as possible to the same column.
- This command is normally bound to the <Down> key.
-
- MOVE LEFT
-
- Moves the cursor left one character position. If the cursor is at
- the beginning of a line, it will wrap to the end of the previous
- line. Normally bound to the <Left> key.
-
- MOVE RIGHT
-
- Moves the cursor right one character position. If the cursor is at
- the end of a line, it will wrap to the beginning of the next line.
- This command is normally bound to the <Right> key.
-
- MOVE WORD
-
- Moves the cursor to the beginning of the next word in the current
- direction. If the direction is Forward, it will move toward the
- end of the buffer; if Reverse, toward the beginning of the buffer.
-
- The screen will either scroll or repaint depending on the state of
- Select. If Select is active, the screen will be redisplayed. If
- Select is not active, scrolling will take place to keep the cursor
- on the fourth line from the top or bottom of the window.
-
-
-
-
-
-
-
-
-
-
-
-
-
-
-
-
-
-
-
-
-
- - 18 -
-
-
-
- p E D I T P L U S C O M M A N D S
-
-
- 2. Text Manipulation
-
- These commands are used to manipulate text - insert new text and
- change the form of existing text.
-
- INSERT CHAR
-
- This is the default when one of the typing keys is pressed. In
- Insert mode, the character will be inserted into the buffer at the
- current cursor position; text to the right of the cursor is
- "shoved over" to make room. In Overstrike mode, the character is
- simply overwritten.
-
- pEDIT uses automatic word wrap to keep text between the defined
- margins as you type. If a word will not fit inside the current
- right margin, it will be moved to the start of the next line. The
- first line of a paragraph will be automatically indented if this
- parameter has been set via the SET PINDENT command.
-
- When the Tab key is pressed, the cursor will move to the next tab
- stop. Only standard tab stops at every eighth column are currently
- supported. Other control characters are displayed as the ASCII
- symbol.
-
- OPEN LINE
-
- Opens up a new (empty) line for text insertion. The end result is
- the same as pressing <Enter> followed by <Left> except that no
- indenting will take place.
-
- FILL PARA (B)
-
- Reformats a paragraph or portion of a paragraph to fit within the
- defined margins, resulting in a ragged right margin. Paragraph
- indenting is honored for the first line. Tabs are ignored. Use
- this command after you have inserted or deleted text or changed
- margins.
-
- The SET MARGINS and SET PINDENT commands are used to set the text
- margins and paragraph indent, respectively. Reformatting begins at
- the current line and stops at the end of the paragraph. A para-
- raph is defined as contiguous text bounded by empty lines both
- above and below.
-
- JUSTIFY PARA (B)
-
- Fully justifies a paragraph or portion of a paragraph to fit with-
- in the defined margins, resulting in both smooth left and right
-
-
- - 19 -
-
-
-
- margins. Paragraph indent is normally not used with justified text
- but is honored if set. Tabs are ignored. Text is not automatically
- justified as you type; this command is meant to be used to justify
- paragraphs after they have been entered.
-
- The SET MARGINS command is used to set the left and right margins.
- Reformatting begins at the current line and stops at the end of
- the paragraph. A paragraph is defined as contiguous text bounded
- by empty lines both above and below.
-
- INDENT
-
- This function is very useful in programming when you want to in-
- dent a section of code in or out without having to manually edit
- each line. Indenting is by levels where one level is 4 character
- positions or one-half a tab stop. INDENT uses tabs and spaces to
- indent the line to the desired offset.
-
- To use INDENT (1) position the cursor to the start of the first
- line, (2) toggle Select on, (3) highlight the entire range of
- lines to be indented and (4) issue the "INDENT" or "INDENT n"
- command. Specify the number of levels (n) as an integer - positive
- indents to the right, negative to the left.
-
- AUTO INDENT
-
- This function is very useful in programming. It is used to auto-
- matically indent a new line the same as the current line. pEDIT
- uses the same leading whitespace (spaces and tabs) as the current
- line. AUTO INDENT is normally used at the end of a line but the
- command can be issued anywhere. Normally bound to <Ctrl-Enter>.
-
- LEFT LINE
-
- Aligns the current line (the line the cursor is on) flush with
- the left margin. Only spaces are used to move the line to the
- appropriate offset.
-
- CENTER LINE
-
- Centers the current line (the line the cursor is on) between the
- defined margins. Only spaces are used to move the line to the
- appropriate offset.
-
- RIGHT LINE
-
- Adjusts the current line (the line the cursor is on) to be flush
- with the right margin. Only spaces are used to move the line to
- the appropriate offset.
-
-
-
-
- - 20 -
-
-
-
- CAPITAL WORD
-
- Capitalizes the current word starting at the current position
- within the word. The capitalization does not start at the begin-
- ning of the word; this is to allow, for example, 'Compuserve' to
- be changed to 'CompuServe'.
-
- LOWER WORD
-
- Converts the current word to lowercase starting at the current
- position within the word. All characters from the cursor to the
- end of the word will be changed to lowercase.
-
- UPPER WORD
-
- Converts the current word to uppercase. All characters from the
- cursor to the end of the word will be changed to uppercase.
-
- QUOTE CHAR
-
- This function is used to enter special characters into the text.
- pEDIT prompts with "Key code (1-255): "; at this point type in the
- decimal Ascii character value and press <Enter>. For example, to
- insert a form feed (Ctrl-L) you would enter the value 12.
-
- The feature can also be used with Find and Replace. To find a line
- feed (Ctrl-J) if the QUOTE CHAR key is <Ctrl-V>, press the DO
- COMMAND key and enter "FIND <Ctrl-V>10<Enter>".
-
- The LIST ASCII command displays the codes for all 255 characters.
- Extended keys such as the PC keypad and function keys cannot be
- quoted. The graphics characters (those above Ascii 127) cannot be
- entered by the very strange method of holding down the Alt key and
- entering the decimal value of the character on the numeric keypad.
-
- TRANS CHAR
-
- Transposes (swaps) two characters of text within a line. The
- cursor must be on the second character when you issue the command.
- The cursor cannot be positioned past the end of the line.
-
-
-
-
-
-
-
-
-
-
-
-
-
- - 21 -
-
-
-
- p E D I T P L U S C O M M A N D S
-
-
- 3. Text Deletion
-
- These commands are used to erase existing text and to restore
- deleted text. Deletion can be by character, word or line.
-
- ERASE CHAR
-
- Deletes the current character, i.e. the character the cursor is
- on. The action is dependent on the current mode. In Insert mode,
- the character is deleted and text to the right of the cursor is
- shifted left to "fill in the hole". In Overstrike mode, the char-
- acter is replaced by a space.
-
- ERASE PREV
-
- Deletes the previous character - the character to the left of the
- cursor. In Insert mode, the character is deleted and text to the
- right of the cursor is again shifted toward the left. In Over-
- strike mode, the character is replaced by a space. The command is
- permanently bound to the <BackSpace> key.
-
- ERASE WORD
-
- Deletes text from the current position in a word to the end of the
- word. The current mode and direction have no effect on the action
- taken; deletion is always toward the end of the word.
-
- ERASE LINE
-
- Erases a line or portion of a line. If the cursor is at the begin-
- ning of a line, the entire line (including the end of line marker)
- is erased and stored in the text buffer. If the cursor is not at
- the beginning of a line, deletion is from the current position to
- the end of the line.
-
- RESTORE TEXT
-
- Restores the text last deleted by ERASE WORD or ERASE LINE. This
- text is stored in a special text buffer for later restoration.
- This text buffer is rebuilt after every action so only the last
- erasure can be restored.
-
- This command along with REMOVE TEXT provide an "undo" capability.
- It is very unlikely that anyone would ever need to "undo" hundreds
- of editing operations. A better approach is to "Save early, save
- often" so you can fall back to the point of the last save.
-
-
-
-
- - 22 -
-
-
-
- p E D I T P L U S C O M M A N D S
-
-
- 4. Searching
-
- These commands are used to search for text and to replace one text
- string by another. A limited wild card facility permits matching
- the beginning and end of line. The SET SCOPE command determines if
- the searching is to be local (the current buffer) or global (all
- buffers).
-
- FIND (B)
-
- FIND is used to search for a text string. To initiate this func-
- tion, press the FIND key and respond to "String to find", or press
- DO COMMAND and enter "FIND <text>". The direction of the search
- will be in the current direction. You can cancel an active FIND
- operation by pressing the ABORT key.
-
- If the target string is all lowercase, the operation will be case-
- insensitive; that is 'pedit' will match all of 'pedit', 'pEDIT'
- and 'PEDIT'. If, however, the target contains any uppercase
- characters, the match will be exact, i.e. 'pEDIT' matches only
- 'pEDIT'.
-
- Special symbols are used to match beginning of line (bol) and end
- of line (eol). Use '\\<' for bol and '\\>' for eol. For example,
- '.\\>' matches a period only if it is at the end of a line.
-
- FINDNEXT (B)
-
- Searches for the next occurrence of the last search string you
- specified. It is best to have FINDNEXT bound to a key so only a
- single key press is required to repeat the last search operation.
-
- REPLACE (B)
-
- pEDIT has a very powerful search and replace function. To initiate
- it, either press the REPLACE key and reply to the "Old string:"
- and "New string:" prompts, or press DO COMMAND and enter "REPLACE
- <old> <new>".
-
- pEDIT will search for each occurrence of 'old' and prompt you with
- "Replace (Y)es (N)o (A)ll (L)ast (Q)uit: "
-
- Y, Enter - replace this occurrence
- N - skip this replacement
- A - replace all occurrences from this point
- L - make this the last replacement and quit
- Q - quit.
-
-
-
- - 23 -
-
-
-
- Matching the old string will follow the rules listed for the FIND
- command. The same wild cards that are useable in FIND may be
- specified for the 'old' string only.
-
-
-
-
-
-
-
-
-
-
-
-
-
-
-
-
-
-
-
-
-
-
-
-
-
-
-
-
-
-
-
-
-
-
-
-
-
-
-
-
-
-
-
-
-
-
-
-
-
-
- - 24 -
-
-
-
- p E D I T P L U S C O M M A N D S
-
-
- 5. Files
-
- These commands pertain to the reading and writing of disk files.
- You can load in a file, save a buffer to disk and change the file
- name associated with a buffer.
-
- Up to 16 files can be loaded at one time. Note that a buffer can-
- not be "released" because pEDIT cannot currently free up memory
- once it has been allocated.
-
- GET FILE (B)
-
- Loads in a file from disk for editing. pEDIT supports wildcard
- file specifications of the type '*.*' and '*.TXT'. If more than
- one file matches the specification, you will be presented with a
- list of all matching file names in alpha order. To select a file,
- use the arrow keys, type in the first letter, or click on it with
- the left mouse button. Press <Enter> or double click to load the
- highlighted file. Press the ABORT key to cancel.
-
- If no matching file exists, pEDIT will display "Creating file". If
- the file does exist, it will be loaded into memory. It is very
- important to realize that the file itself is still on disk and
- will remain unchanged unless you save a modified buffer using the
- WRITE FILE command.
-
- INCLUDE FILE
-
- Reads in the specified file from disk and inserts it into the
- buffer starting at the current cursor location. The result is the
- same as if the user typed in the text contained in the file.
-
- INCLUDE FILE should be used only for relatively small files. The
- function uses the normal INSERT CHAR routine, not the much faster
- GET FILE which loads text directly into memory.
-
- WRITE FILE (B)
-
- Saves the contents of the current buffer to disk without ending
- the editing session. If a file name has not yet been specified,
- pEDIT will ask for one.
-
- pEDIT PLUS verifies that there is sufficient disk space BEFORE
- starting the save operation. The Error Handling Section has a full
- description of what to do if you get an error while saving a file.
-
- You can change the name of the associated file at any time by
- using the RENAME FILE command.
-
-
- - 25 -
-
-
-
- RENAME FILE
-
- Changes the name of the disk file associated with the current
- buffer. The new name will be used at the time of the next WRITE
- FILE operation. The buffer name is also changed to reflect the
- new file name if that buffer name is not already in use.
-
- Use RENAME FILE when you want to save a file under a name other
- than the one the it was called up under.
-
-
-
-
-
-
-
-
-
-
-
-
-
-
-
-
-
-
-
-
-
-
-
-
-
-
-
-
-
-
-
-
-
-
-
-
-
-
-
-
-
-
-
-
- - 26 -
-
-
-
- p E D I T P L U S C O M M A N D S
-
-
- 6. Buffers
-
- These commands affect how text is viewed. You can pick which
- buffer to view, set the mode and direction for a buffer, and so
- on.
-
- SHOW BUFFER (B)
-
- Displays detailed information about the current buffer: the buffer
- name, associated file name, current mode/direction, number of
- lines and characters of text, etc. The status line also shows the
- pEDIT version number.
-
- BUFFER (B)
-
- Use this command to switch between buffers. You will be presented
- with a BUFFER window containing the names of all buffers except
- the COMMAND buffer. The name of the first User buffer will be
- highlighted. To select a buffer, use the up and down arrow keys,
- type in the first letter of a buffer name or click on the name.
- Press <Enter> or double click to move to the selected buffer. You
- can also Press ABORT to cancel.
-
- TRIM BUFFER
-
- This function 'trims' the current buffer by removing trailing
- blanks from all lines of text.
-
- TRIM BUFFER is useful in any document where a left margin has been
- defined. pEDIT automatically indents every line to the specified
- left margin, which can result in "empty" lines between paragraphs.
- These empty lines can take up a lot of space in a large document.
-
- CHANGE MODE
-
- Used to toggle between Insert and Overstrike modes. If the mode is
- Insert when the command is given, it will change to Overstrike and
- vice versa.
-
- CHANGE DIR
-
- Use this command to toggle between the Forward and Reverse
- directions. Note that only FIND, FINDNEXT, REPLACE and MOVE WORD
- use the buffer direction.
-
- MARK
-
- Used to mark a particular place in a buffer so you can return to
-
-
- - 27 -
-
-
-
- it at some later time. Sometimes called a bookmark; there can be
- only one marker in each buffer. pEDIT tries to stay as close as
- possible to the original mark as text is inserted and deleted.
-
- GOTO MARK
-
- This command moves to the position (line and offset) defined by
- the last MARK command.
-
- LINE
-
- The LINE command is used to "goto" a particular line in the cur-
- rent buffer. Enter "LINE nn" to move to line number nn; if you
- enter LINE by itself, pEDIT will prompt for a line number.
-
-
-
-
-
-
-
-
-
-
-
-
-
-
-
-
-
-
-
-
-
-
-
-
-
-
-
-
-
-
-
-
-
-
-
-
-
-
-
- - 28 -
-
-
-
- p E D I T P L U S C O M M A N D S
-
-
- 7. Windows
-
- The window functions control the number of windows on screen and
- let you select the current window. A window can be panned up,
- down, left or right to view any portion of a buffer.
-
- ONE WINDOW
-
- This function 'unsplits' the screen. If there are 2 windows on
- screen, the current window - the one the cursor is in - becomes
- the only window. The current window will occupy the full screen.
- The line the cursor was on when the command was issued becomes the
- top line of the window.
-
- TWO WINDOWS
-
- 'Splits' the screen if there is only one window visible. Both
- windows will initially show the same number of lines of the
- current buffer. The cursor will be moved to the other window,
- anticipating that you want to load in another file.
-
- OTHER WINDOW (M)
-
- If the screen is split, this command will move the cursor to the
- other window. The cursor will move to the row and column stored
- the last time the cursor was in the window.
-
- If you have a mouse, click anywhere in the other window to move to
- that window.
-
- PREV LINE (M)
-
- Scrolls the current window up one line. This command is normally
- accessed only with a mouse, by clicking on the UpArrow symbol at
- the top of the Scroll Bar.
-
- PREV SCREEN (M)
-
- Moves the text window back one screen towards the beginning of the
- buffer. This command should be bound to the <PgUp> key as it means
- "Page Up". The screen is repainted rather than scrolled.
-
- NEXT LINE (M)
-
- Scrolls the current window down one line. This command is normally
- accessed only with a mouse, by clicking on the DownArrow symbol at
- the bottom of the Scroll Bar.
-
-
-
- - 29 -
-
-
-
- NEXT SCREEN (M)
-
- Moves the text window forward one screen towards the end of the
- buffer. This command should remain bound to the <PgDn> key as it
- means "Page Down". Again, the screen is repainted rather than
- scrolled.
-
- SHIFT LEFT (B)
-
- Moves the window horizontally to the left (toward the left margin)
- the specified number of columns. If no parameter is specified, the
- shift amount will be 40 columns.
-
- SHIFT RIGHT (B)
-
- Shifts the screen horizontally to the right - toward the end of
- the line - by the number of columns you specify. This is to permit
- viewing text past column 78. If no argument is specified, the
- screen will be shifted 40 columns. The shift value is limited only
- by the maximum line length of 32767 characters.
-
-
-
-
-
-
-
-
-
-
-
-
-
-
-
-
-
-
-
-
-
-
-
-
-
-
-
-
-
-
-
-
-
- - 30 -
-
-
-
- p E D I T P L U S C O M M A N D S
-
-
- 8. Cut and Paste
-
- pEDIT provides another "undo" capability in addition to restoring
- erased text. A block of text can be "cut" and stored in a "paste"
- buffer (also called the clipboard) for later retrieval. Other com-
- mands are available to copy the selected text without removing it,
- and to delete text without storing it.
-
- Important: the maximum size of a block that can be stored on the
- clipboard using the REMOVE TEXT and STORE TEXT commands is limited
- by available memory.
-
- SELECT TEXT (M)
-
- This is a toggle that turns the select state on/off. If the state
- is off, it will be turned on and vice versa. Selected text is
- highlighted in reverse video as the cursor is moved. Select is
- automatically turned off after REMOVE TEXT, STORE TEXT and WIPE
- TEXT commands. To cancel the selection, i.e. turn the highlighting
- off, simply issue the command again.
-
- To select text with the mouse, move the mouse pointer to the start
- of the desired block. Hold the left button down for at least 1/2
- second, then "drag" the mouse in any direction while continuing
- to hold the left button down. You can even scroll up or down while
- selecting by dragging the mouse pointer to the row just above or
- below the text window.
-
- REMOVE TEXT (B)
-
- Removes (cuts) the selected text and stores it to the clipboard
- (paste buffer). The clipboard is rebuilt every time REMOVE TEXT is
- invoked; therefore, only the most recently deleted text can be
- reclaimed.
-
- STORE TEXT
-
- Copies the selected text to the clipboard without removing from
- the buffer. Use this command whenever you want to make a copy of
- some text without deleting it.
-
- WIPE TEXT
-
- Deletes the highlighted block without copying it to the clipboard.
- WIPE TEXT is much faster than REMOVE TEXT because the paste buffer
- does not have to be rebuilt. This command is especially useful for
- deleting large amounts of text; use it when you have no need to
- get the text back. There is no limit on the size of the block that
- can be erased.
-
- - 31 -
-
-
-
- INSERT HERE (B)
-
- Inserts text from the clipboard into the current buffer starting
- at the current cursor position. Note that INSERT HERE can be in-
- voked more than once to make multiple copies of the stored text.
-
-
-
-
-
-
-
-
-
-
-
-
-
-
-
-
-
-
-
-
-
-
-
-
-
-
-
-
-
-
-
-
-
-
-
-
-
-
-
-
-
-
-
-
-
-
-
-
- - 32 -
-
-
-
- p E D I T P L U S C O M M A N D S
-
-
- 9. Key Macros
-
- pEDIT's key macro facility lets you automate repetitive tasks.
- With the following commands you can start a "learn" sequence and
- pEDIT will "remember" all the keystrokes that were entered. You
- can then "play back" the macro to replay the keystrokes.
-
- Key macros can be saved permanently to disk, making it possible to
- have several pre-defined macros available for use.
-
- LEARN
-
- The LEARN command is used to start recording keystrokes. The rec-
- ording will continue until the REMEMBER command is given. pEDIT
- will store all typing keys, function keys and special keys such as
- control keys. Note that mouse button presses are not stored.
-
- Any key can be stored in a pEDIT macro. The only restriction is
- that a macro containing a REPEAT command cannot itself be repeated.
-
- REMEMBER
-
- Used to end the keystroke recording started by LEARN. pEDIT will
- ask for a key to bind to; press any of the definable keys on the
- keyboard. You cannot bind to the Tab, Enter or BackSpace keys.
-
- A macro must also not be bound to a key that is contained within
- the macro. If this happens, the macro routine will go into a loop
- and probably crash the system.
-
- SAVE MACRO
-
- Saves the currently defined key macro to disk. Enter only a file
- name; pEDIT automatically adds the extension .PM1. The editor will
- write the macro file in the directory pointed to by the current
- PEDIT PATH.
-
- If a macro file of the same name already exists, you will be given
- the chance to overwrite it or cancel.
-
- EXECUTE
-
- Executes the macro previously defined by LEARN and REMEMBER. When
- this command is issued, the keystrokes are 'replayed' as if you
- entered them. There are two forms of this command: one for a key
- macro, one for a disk macro. See the 'Macro Facility' section for
- more information.
-
-
-
- - 33 -
-
-
-
- EXECUTE by itself is used for the single key macro. A command of
- the form "EXECUTE filename" invokes a disk macro. Here, "filename"
- is a valid DOS file name up to 8 characters in length without an
- extension. pEDIT automatically adds the file type .PM1 to all disk
- macro file names.
-
-
-
-
-
-
-
-
-
-
-
-
-
-
-
-
-
-
-
-
-
-
-
-
-
-
-
-
-
-
-
-
-
-
-
-
-
-
-
-
-
-
-
-
-
-
-
-
- - 34 -
-
-
-
- p E D I T P L U S C O M M A N D S
-
- 10. Miscellaneous
-
- DO COMMAND (B)
-
- When the "DO" key is pressed the editor will respond with the
- 'Command: ' prompt. At this point you can enter any valid pEDIT
- command. Commands can be upper- or lower-case or mixed. Note that
- commands must be entered in full with spaces in between words. You
- can exit Command Mode without doing anything by pressing <Enter>
- after the prompt.
-
- The Command line is a one-line window into the COMMAND buffer. All
- defined keys can be used on the command line for editing the cur-
- rent line. Use MOVE UP and MOVE DOWN to scroll through the stored
- commands.
-
- RECALL
-
- Used to recall the last command given via DO COMMAND. The end
- result is the same as pressing the DO COMMAND key followed by the
- MOVE UP with one important difference; the previous command is
- copied to the current command line. The command can of course be
- edited before pressing <Enter> to begin execution.
-
- DO BUTTON
-
- Permits keyboard access to the ButtonBar for those users without a
- mouse. This function is permanently bound to the <Shift-Esc> key
- and should not be issued from the command line. When this key is
- pressed, the first button will be selected and pEDIT will wait for
- your input. Use the <Left> and <Right> keys to move from button-to-
- button, and press <Enter> to accept or ABORT to cancel.
-
- ABORT
-
- pEDIT has a user-definable ABORT key which must be defined in the
- initialization file. The actual key used depends on the configur-
- ation; ABORT is not 'hard-wired' to <Ctrl-C> because WordStar uses
- <Ctrl-C> as a command key.
-
- ABORT can be used to abort out of any REPEAT, FIND, FINDNEXT or
- REPLACE loop. You can also use it to cancel out of the DO BUTTON
- function, or any BUFFER, FILES or HELP screen.
-
- REFRESH SCREEN
-
- This command is used to clear and repaint the screen. Use REFRESH
- SCREEN if, for any reason, the screen should be overwritten or
- otherwise obliterated.
-
-
- - 35 -
-
-
-
- DEFINE SHIFT
-
- Defines a shift or "lead-in" key for multi-key commands. pEDIT
- must know when to wait for a second keystroke. A shift key cannot
- be a command key by itself.
-
- The shift keys must be defined in your initialization file before
- other key definitions. Any non-typing key can be a shift key; a
- maximum of 4 shift keys can be defined.
-
- DEFINE KEY
-
- Used to 'bind' a pEDIT command to the key of your choice. Pressing
- the specified key is equivalent to pressing DO COMMAND and typing
- in the associated command. Here, 'command' refers to any valid
- pEDIT command entered in full (no abbreviations) with or without
- parameters.
-
- Keys can be defined dynamically during an editing session or, more
- commonly, specified in your init file. When DEFINE KEY is issued
- from within the editor, pEDIT will ask for a procedure name and a
- key press.
-
- SHOW KEY
-
- Displays the command bound to a key. pEDIT will prompt for a key
- press and display the full command string, if there is one, bound
- to that key.
-
- LIST KEYS
-
- Lists all defined keys and the commands bound to them. pEDIT will
- pause in between screens; press any key to continue to the next
- screen.
-
- LIST ASCII
-
- Displays the complete ASCII character set used by the IBM PC. In-
- cludes the decimal value (1-255), the hexadecimal or "HEX" value
- (01H to FFH) and the character. Very handy for programmers. The
- editor will pause in between screens; press any key to continue to
- the next screen.
-
- DRAW (B)
-
- This function is used to draw lines and boxes on the screen. The
- Mode and Direction indicators on the Status Bar are replaced by
- the text "** DRAWING MODE **". Only a subset of the defined keys
- are recognized:
-
- ABORT Exit drawing mode and return to editing
-
-
- - 36 -
-
-
-
- MOVE UP Move up one line, padding if necessary
- MOVE DOWN Move down one line, padding if necessary
- MOVE LEFT Move cursor left one column
- MOVE RIGHT Move right one column with padding
- MOVE HOME Position to start of line
- MOVE END Position cursor to end of line
- - Draw a single line/box using graphics chars
- = Draw a double line/box using graphics chars
- + Draw a line or box using standard chars
-
- See the section 'Drawing With pEDIT PLUS' for more information.
-
- REPEAT
-
- Lets you repeat any key press up to 32767 times. Only the next
- single key press is repeated.
-
- The repeat count is shown by 'Repeat: ' on the message line. Use
- <BackSpace> to correct the count; set the count to zero if you
- wish to cancel.
-
- You can exit a REPEAT loop by pressing the ABORT key.
-
- SET AUTOSAVE
-
- The autosave feature can be used to automatically save your work
- to disk. If autosave is active, a WRITE FILE will be performed
- periodically to the current buffer if changes have been made. The
- buffer will also be saved when a new file is loaded or you switch
- buffers.
-
- The usage is "SET AUTOSAVE value". A value of zero turns the
- autosave feature off; a value in the range 1-30 defines a save
- interval of 1 to 30 minutes.
-
- SET COLOR
-
- Lets you choose foreground and background colors for your editing
- session. For monochrome and CGA displays, the only legal color
- combinations are Black-on-White and White-on-Black.
-
- Only the basic 16 colors are supported on EGA/VGA color displays.
- The usage is "SET COLOR fground bground". See the Appendix for a
- list of color codes.
-
- SET CURSOR
-
- Lets you choose an underline or block cursor style to suit your
- personal needs. The usage is "SET CURSOR uline|block".
-
- SET DISPLAY
-
-
- - 37 -
-
-
-
- Used to override pEDIT's video display type detection. This com-
- mand can only be used in the initialization file. Use it only if
- pEDIT cannot correctly identify your video type. The syntax is
- "SET (DISPLAY, n)" where n = 0 (text); 2 (CGA); 9 (color EGA/VGA);
- 10 (mono EGA/VGA).
-
- SET LINES
-
- Lets you choose the number of lines of text that are shown on-
- screen. All displays support 25 lines; 43 line mode requires EGA
- or VGA, while 50 line mode (text mode only) requires VGA. Screen
- writing and scrolling are generally much slower in 43-and 50-line
- modes. This command cannot be used when the screen is split. The
- usage is "SET LINES 25|43|50".
-
- SET MARGINS
-
- Lets you set left and right text margins; the right margin con-
- trols where text wraps. The default margins are 1 and 80. The left
- margin must be greater than zero and the right margin has to be
- greater than the left. The usage is "SET MARGINS left right".
-
- SET PINDENT
-
- Used to set the paragraph indent, i.e. the number of columns by
- which to indent the first line of a paragraph. The usage is "SET
- PINDNT nn" where nn is zero or a positive integer.
-
- SET SCOPE
-
- Specifies the "scope" for all FIND and REPLACE operations. If the
- scope is Local, only the current buffer will be searched. If how-
- ever the scope is Global, all user buffers will be searched and
- 'Global' will show on the status line. The format of this command
- is "SET SCOPE local|global".
-
- Things can quickly get out of hand if some buffers are searched in
- a forward direction while others are searched in reverse. For this
- reason, the direction for all buffers is temporarily set to
- Forward during a global search.
-
- SET VIDEO
-
- Lets you switch between text and graphics mode if you have a
- graphics display. pEDIT PLUS will start up in graphics mode if it
- detects a CGA/EGA/VGA display; you can override this if you prefer
- the speed of text mode to the graphical interface. The usage is
- "SET VIDEO text|graphics".
-
- PRINT (R)
-
-
-
- - 38 -
-
-
-
- Provides the ability to print directly from within pEDIT PLUS.
- This is done by interfacing to the PRINT utility included with DOS
- 3.0 and greater. This function is available only in registered
- versions of pEDIT. Use this command to print the contents of the
- current buffer, print a selected portion of the current buffer,
- delete a file from the print queue or cancel all print jobs in the
- queue. The syntax is "PRINT buffer|block|delete|cancel".
-
- If the printer is off-line or out of paper, the PRINT DELETE and
- PRINT CANCEL commands may not complete correctly. pEDIT should
- resume after the problem is fixed. See the section 'Printing from
- pEDIT PLUS' for more information.
-
- SHOW PRINTER (R)
-
- Displays the status of all jobs in the print queue in a special
- PRINTER window. pEDIT shows a maximum of 10 jobs; this is the
- default number of queue entries in the DOS PRINT utility. If there
- are more than 10 files queued - the maximum is 32 - they will not
- be shown. Press any key or mouse button to return to editing.
-
- DOS (B)
-
- This function 'shells' you to DOS or passes a command to DOS for
- execution. All text is swapped out to disk, and a second copy of
- the command processor is loaded to process commands. Refer to the
- section 'Extended DOS Shell' for more information.
-
- If "DOS" is given without parameters, you will be shelled to DOS
- and will see the DOS prompt. You may then enter DOS commands and
- do anything you can do at the operating system level. Type 'EXIT'
- to return to the editor exactly as you left it.
-
- If parameters are specified, the command will be passed to DOS for
- execution and the output will be shown in the DOS buffer.
-
- HELP (B)
-
- Provides complete on-line help for every pEDIT PLUS command. pEDIT
- looks for a help file named PEDIT.HLP in the directory pointed to
- by the PEDIT PATH.
-
- You will be presented with a HELP window containing an alpha list
- of all pEDIT commands. Use the arrow keys, press the first letter
- of the command or click the left mouse button to highlight the
- topic you want help with; press <Enter> or double click to select
- that topic. The function can be cancelled by pressing the ABORT
- key.
-
- ALTHELP
-
-
-
- - 39 -
-
-
-
- Displays the contents of the files PEDIT.BTN and PEDIT.KEY in
- BUTTON and KEYBOARD windows, respectively. The editor looks for
- these two files in the directory specified by the PEDIT PATH.
-
- Provides help for the ButtonBar and the keyboard (usually a
- keyboard diagram and/or a list of the keys you have defined).
-
- RULER
-
- Toggles an on-screen ruler on and off. The ruler temporarily over-
- writes the status line at the bottom of the window.
-
- QUIT (B)
-
- Aborts an editing session. Abort MEANS abort - any changes you
- have made will be lost. If any User (non-system) buffers have been
- modified, pEDIT gives you the option of not quitting by displaying
- "Buffer(s) modified - quit (Y/N)? ". Enter Y to abort, N to cancel
- and resume editing.
-
- EXIT
-
- Terminates the editing session and returns you to DOS. The current
- buffer is automatically written to disk if it has been modified.
- If any of the other user buffers have been altered, pEDIT asks you
- one at a time if you want to write (save) them. Answer 'Y' to save
- the buffer, 'N' to skip it.
-
-
-
-
-
-
-
-
-
-
-
-
-
-
-
-
-
-
-
-
-
-
-
-
-
-
- - 40 -
-
-
-
- M A C R O F A C I L I T Y
-
- 1. Macro Types
-
- pEDIT supports two different kinds of macros. The first is a key
- macro. The primary use of this type of macro (of which there can
- be only one) is to automate one-time tasks. If you find you are
- using the same stored keystrokes over and over, the macro should
- be given a name and saved to disk.
-
- The second type of macro is a disk macro. Start by setting up a
- key macro as above; experiment until you get it working the way
- you want. Then, issue the SAVE MACRO command and pick a file name.
- The name must be a standard DOS filename of up to 8 characters.
- Do not include a file type; pEDIT automatically adds the extension
- PM1. If the macro file already exists, you will be given a chance
- to overwrite the file or abort.
-
- Disk macros are used to automate things you do all of the time.
- Let's say you do medical transcription and constantly have to type
- in the phrase 'blood pressure'. Easy - define a disk macro 'BP' to
- automatically enter the text for you.
-
- Another use for disk macros is to extend the editor - to give it
- a capability it doesn't have. Two of the sample macros provide
- something that is not built-in to pEDIT: the ability to scroll the
- OTHER window up/down when the screen is split.
-
-
- 2. Macro Execution
-
- A key macro is invoked by issuing the command EXECUTE without
- any parameters.
-
- Disk macros are executed via "EXECUTE filename" where filename
- is the name the macro was saved under. Again, do not specify a
- file type. pEDIT looks for the macro files in the directory
- pointed to by the PEDIT PATH.
-
-
- 3. Sample Macros
-
- pEDIT is supplied with four sample macros which will be in-
- stalled under the following names. As usual, XXX refers to the
- configuration type (EMC, QUI, STD, WPF or WST):
-
- XXXLETTR.PM1 Sets the left margin to 10, the right
- margin to 70 and the paragraph indent
- to 4 for a letter with 1" margins
-
- XXXOTHUP.PM1 Scrolls the other window up
-
-
-
- - 41 -
-
-
- XXXOTHDN.PM1 Scrolls the other window down
-
- XXXWREV.PM1 Moves one word in the reverse direction;
- temporarily changes the buffer direction
- to Reverse - so you must start Forward
-
-
- 4. Converting Disk Macros
-
- pEDIT PLUS 1.1 uses a different disk macro file format than did
- earlier versions. The macros supplied with v1.1 are in the new
- format; any macros you have created will have to be converted. A
- conversion program PMCONVRT is included for this purpose.
-
- The program file PMCONVRT.EXE will be in the directory where you
- installed pEDIT. PMCONVRT will automatically convert all of the
- PMC files it finds in the current directory to the new PM1 format;
- the original files will be retained with the PMC extension.
-
- PMCONVRT assumes that <Ctrl-I> is <Tab>, <Ctrl-M> is <Enter>,
- <Ctrl-H> is <BackSpace> and <Ctrl-J> is <Ctrl-Enter>. There are
- some cases where PMCONVERT will not be able to convert an old file
- correctly and you will have to recreate it. If the DO COMMAND key
- has changed (this happened with the STD configuration) things
- obviously won't work right. Also, multi-key combination can't be
- translated because PMCONVRT can't know what shift keys are in use.
-
- If you installed pEDIT in the default \PEDIT directory you would
- run the the conversion program as follows:
-
- CD \PEDIT
- PMCONVRT
-
- PMCONVRT will convert up to 32 files in a single pass. If you
- have more than 32 macros, you will have to rename the first 32 to
- an extension other than PMC and run the program again. After you
- are confident that the conversion was successful, you can delete
- the files *.PMC and PMCONVRT.EXE.
-
-
-
-
-
-
-
-
-
-
-
-
-
-
-
- - 42 -
-
-
-
- D E F I N I N G K E Y S I N
- p E D I T P L U S
-
-
- Virtually any key (including any combination of Shift, Control
- and Alt keys) on the keyboard can now be defined thanks to pEDIT's
- new keyboard interrupt handler. pEDIT is able to do this by inter-
- cepting the key press (which would normally be processed by the
- BIOS) directly in hardware.
-
- The only keys that can't be defined are Tab, Enter and Space
- (typing keys), <BackSpace> and <Shift-Esc>. You can define ANY
- other key... including ones you shouldn't(!) After pEDIT has pro-
- cessed a key, it is passed on to the BIOS to be handled in the
- normal way. If this wasn't done, you couldn't reboot with the
- three fingered salute (Ctrl-Alt-Del) or print the screen (PrtScr).
-
- You should therefore not define any keys that have a special
- meaning to the system; your system manuals should have a list of
- these keys. Also, you wouldn't want to define any "hot" keys for
- TSRs such as screen blankers. Finally, it is recommended that you
- not define any of the keys which have a special mening to Micro-
- soft Windows: <Alt-Space>, <Alt-Tab>, <Alt-Enter>, <Alt-Esc>,
- <Ctrl-Esc>, etc.
-
- It should be noted that certain keys are not seen as identical
- as they would be under the BIOS. The following keys are no longer
- equivalent: <Ctrl-H> and <BackSpace>, <Ctrl-I> and <Tab>, <Ctrl-M>
- and <Enter>. This means that you can define <Ctrl-H>, <Ctrl-I> and
- <Ctrl-M> just like any other Control key.
-
- This new capability opens up many new possibilites. pEDIT can
- now emulate any editor or word processor that uses 2-key commands.
- And, this is what lets the STD configuration be CUA-compliant. Un-
- fortunately, WordPerfect uses 3- and 4-key combinations, and so
- the emulation is approximate.
-
-
-
-
-
-
-
-
-
-
-
-
-
-
-
-
-
- - 43 -
-
-
-
- E X T E N D E D D O S S H E L L
-
-
- pEDIT has an intelligent DOS shell which provides up to 350k of
- free memory on a 640k machine when shelled to DOS. This provides
- sufficient free memory to complile from within pEDIT and to run
- large programs.
-
- All text is temporarily 'swapped' out to disk and the memory is
- released before calling DOS. When the user types 'EXIT' to return
- to the parent program, the text storage is reallocated and re-
- loaded from these swap files.
-
- pEDIT checks to make sure there is sufficient disk space to hold
- the swap files. If not, the function will be cancelled. It is very
- important that you not delete the temporary swap files, which are
- stored in the PEDIT PATH with names of PED$$$n.TMP where n = 0-4.
- Note that pEDIT automatically deletes these files after they have
- been reloaded into memory.
-
- DO NOT run any TSR (Terminate and Stay Resident) programs when
- shelled to DOS. This is a sure way to lock up your computer. Some
- examples of TSRs are the DOS PRINT utility and mouse drivers such
- as MOUSE.COM.
-
-
-
-
-
-
-
-
-
-
-
-
-
-
-
-
-
-
-
-
-
-
-
-
-
-
-
-
-
- - 44 -
-
-
-
- D R A W I N G W I T H
- p E D I T P L U S
-
-
- pEDIT PLUS now supports automatic line and box drawing in 3
- different styles. These figures can be drawn using graphical
- single lines, graphical double lines or ordinary text characters:
-
- ┌───────┐ ╔═══════╗ +-------+
- │ │ ║ ║ | |
- └───────┘ ╚═══════╝ +-------+
- (-) (=) (+)
-
- Follow these three simple steps to draw:
-
- 1. Issue the DRAW command or click on the <DRW> Button to enter
- drawing mode; the starting cursor position (the anchor) will
- remain highlighted in reverse video. The Status Bar will show
- "** DRAWING MODE **" until you finish or abort.
-
- 2. Use the MOVE UP, MOVE DOWN, MOVE LEFT, MOVE RIGHT, MOVE HOME
- and MOVE END keys (the mouse can't be used here) to move to
- the opposite end of the line or box. You can move in any
- direction. If you move past the end of a line, the line will
- be padded with spaces to extend it to the desired offset.
-
- 3. Press one of the three style keys dash (-), equals (=) or
- plus (+) shown above to select the desired style and complete
- the drawing. You can abort without drawing anything by pres-
- sing the ABORT key.
-
- Your printer may not be able to print the graphical single and
- double lines because they use the special graphical characters
- above decimal 127. However, any printer can print the plain text
- style (+-----+).
-
- If you use the auto padding as described above, there is one
- thing to be aware of. As you move to the right, the cursor will be
- on the imaginary end of line, not on the last character of the
- line. You must therefore move one column *past* where you want the
- line or box to be drawn; on the ending line, move back in one col-
- umn so the cursor is on the last character of the line. Note also
- that the figures won't de drawn correctly if the text contains any
- tabs.
-
-
-
-
-
-
-
-
-
- - 45 -
-
-
-
- P R I N T I N G F R O M
- p E D I T P L U S
-
-
- Registered pEDIT PLUS owners can now print directly from the
- program. If you are evaluating a shareware version of pEDIT, you
- will be informed that the PRINT function is only available in the
- registered version. If you need a reason to register, here it is.
-
- pEDIT PLUS is not a $500 word processor and cannot compete with
- programs like WordPerfect which must provide printer drivers for
- hundreds of printers. This would add immeasurably to the size and
- complexity of pEDIT. pEDIT supports printing by interfacing to the
- DOS PRINT utility, which is included with DOS 3.0 and later.
-
- The PRINT program is a TSR which performs "background" printing;
- that is, it can print while you do other things. A maximum of 32
- files can be queued; the default is 10 files. pEDIT will let you
- print one (or more) files while you continue to work. Printing
- will continue even if you shell to DOS or exit.
-
- In order for pEDIT to print correctly, you must install the DOS
- PRINT utility *before* you execute pEDIT. The easiest way to do
- this is to install PRINT in your AUTOEXEC.BAT file at startup:
-
- PRINT /D:LPT1
-
- This example loads the PRINT program into memory and tells it to
- use the first parallel printer LPT1. Valid devices are LPTn, COMn
- and PRN, which is the same as LPT1. Refer to your DOS manuals for
- more information.
-
- Once PRINT has been installed, you can perform the following
- functions from within pEDIT PLUS:
-
- 1. PRINT BUFFER; print the current buffer
-
- 2. PRINT BLOCK; print a selected block of text
-
- 3. PRINT DELETE; delete a file from the queue
-
- 4. PRINT CANCEL; cancel all print jobs in the queue
-
- 5. SHOW PRINTER; examine the print queue.
-
- Important: option (1) will print the file associated with the
- current buffer; you will therefore be asked if you want to save a
- modified buffer before printing.
-
- When printing a block, you must select full lines as explained
- for the INDENT command. pEDIT writes the selected block into the
-
-
- - 46 -
-
-
-
- file PED$$.PRN, which is then printed.
-
- pEDIT currently does not have a repaginate command to insert
- form feeds into a document. Note, however, that you can repaginate
- by defining a macro which moves down the number of lines you want
- per page, and then inserts a form feed (Ascii ^L, decimal 12).
-
-
-
-
-
-
-
-
-
-
-
-
-
-
-
-
-
-
-
-
-
-
-
-
-
-
-
-
-
-
-
-
-
-
-
-
-
-
-
-
-
-
-
-
-
-
-
- - 47 -
-
-
-
- C O M P I L I N G F R O M
- p E D I T P L U S
-
-
- Programs can be compiled from within pEDIT using the built-in
- DOS function. There are several ways to accomplish this; in all
- cases, the output will be placed in the DOS buffer so you can see
- any errors.
-
-
- 1. Manual Invocation
-
- The simplest method is to issue the command(s) from within the
- editor. Unfortunately, a different command line must be typed in
- for every source buffer so this can't be easily automated. pEDIT
- supports simple command substitution to translate
-
- DOS \QBASIC\BC % /S /O ;
-
- to, for example,
-
- DOS \QBASIC\BC C:\BASIC\TEST /S /O ;
-
- pEDIT will substitute the file name associated with the current
- buffer less the file type. The file type (extension) is not in-
- cluded because compilers and linkers typically use the same file
- name but a different file type.
-
-
- 2. Batch File
-
- Another method is to use a DOS batch (BAT) file to perform the
- compilation. This method requires some finagling because there is
- no way to direct all of the the output from a BAT file. Recall
- that pEDIT uses a temporary file (PED$$.TMP) to capture the output
- from a shelled DOS command.
-
- The trick is to redirect the output from your batch file to
- PED$$.TMP. Simply add the text ">>PED$$.TMP" to the end of every
- line in your batch file that displays output. This tells DOS to
- direct the output to PED$$.TMP and to append to the file.
-
-
- 3. Disk Macros
-
- The most elegant way to compile is with pEDIT's disk macros. The
- macros can even automatically step through the compile errors and
- position to each offending line in the source file! This is quite
- impressive considering that no macro language is used.
-
- Only the general method, which requires two macros, can be out-
-
-
- - 48 -
-
-
-
- lined here. The first does the actual compilation and positions
- the DOS buffer to the start of the latest compile statement. The
- second steps through the errors one-at-a-time by moving to the DOS
- window, finding an error string and storing it on the clipboard,
- and returning to the source window and using FIND to position to
- the offending line.
-
- The most difficult part of the second macro is locating the
- errors! Compilers use different error indicators. A caret (^) on
- one line is fairly common to point to the offending part of a
- statement on the line above. Another problem is that a single
- source line can generate several errors.
-
-
-
-
-
-
-
-
-
-
-
-
-
-
-
-
-
-
-
-
-
-
-
-
-
-
-
-
-
-
-
-
-
-
-
-
-
-
-
-
-
- - 49 -
-
-
-
- E R R O R H A N D L I N G
-
- If an error occurs, pEDIT will bring up an ERROR window and
- alert you to one of the following problems.
-
-
- 1. Insufficient Internal Storage
-
- When it is invoked, pEDIT checks to see how much free memory is
- available. This determines the maximum number of lines and char-
- acters of text it can handle. pEDIT informs you whenever 99% of
- either of these values is reached and advises you to "Save your
- work and exit". If you continue to work, you will get the warning
- *every* time text is added. If you ignore the warnings and exceed
- the allocated space, the program will abort.
-
- There is no recovery from this other than to exit (be sure and
- save your work) and start over. pEDIT presently cannot free up
- memory once it has been allocated.
-
-
- 2. Insufficient Disk Space
-
- pEDIT checks for sufficient disk space BEFORE it starts a file
- save operation. If there isn't enough disk space, you will be
- advised to "Increase available space on current drive or change
- file specification via RENAME FILE".
-
- The text is still in memory and has not been lost; however, it
- has *not* been saved to disk. If possible, shell to DOS and delete
- some files to free up space. Or, switch to a different diskette
- that has more room. Or, use the RENAME FILE command to change to
- another drive; for example, if the current file is A:MYFILE.TXT,
- save the file as B:MYFILE.TXT.
-
-
- 3. No Initialization File
-
- pEDIT requires an initilization file for proper operation. The
- default init file is named PEDIT.INI. If this file cannot be
- found, it means that pEDIT has not been properly installed using
- the INSTALL program.
-
- If an initialization file can't be found, pEDIT will start up
- with a minimal configuration so you can communicate with the
- editor. The colors are set to white on blue, and the labelled keys
- such as the cursor keys, <Ins>, <Del>, <PgUp> and <PgDn> are bound
- to their expected functions. Finally, the <Esc> key is defined as
- DO COMMAND.
-
-
-
-
- - 50 -
-
-
-
- M I S C E L L A N E O U S
- L E G A L I T I E S
-
-
- 1. Copyright Notice
-
- This document, other accompanying written and disk-based
- specifications, and all referenced and related program files are
- copyrighted by T. G. Muench.
-
- PC-DOS is a registered trademark of International Business
- Machines Corporation. MS-DOS and QuickBASIC are trademarks of
- Microsoft Corporation. WordPerfect is a trademark of Word Perfect
- Corporation. WordStar is a registered trademark of MicroPro
- International. Other brand and product names are trademarks or
- registered trademarks of their respective holders.
-
-
- 2. Registration
-
- pEDIT PLUS is a "shareware program" and is provided at no charge
- to the user for evaluation. Feel free to share it with your
- friends, but please do not give it away altered or as part of
- another system. The essence of "user-supported" software is to
- provide personal computer users with quality software without high
- prices, and yet to provide incentive for programmers to continue
- to develop new products. If you find this program useful and find
- that you are using pEDIT PLUS and continue to use pEDIT PLUS after
- a reasonable trial period, you must make a registration payment to
- T. G. Muench.
-
- Print the file REGISTER.DOC for complete information on how to
- register for pEDIT PLUS and how to contact the author.
-
-
-
-
-
-
-
-
-
-
-
-
-
-
-
-
-
-
-
-
- - 51 -
-
-
-
- A P P E N D I C E S
-
- A. Key Bindings
-
- 1. Labelled Keys
-
- Many of the labeled keys on the PC keyboard are bound to functions
- common to all configurations. The function bound to these keys
- corresponds to the key name. Keys marked with (*) cannot be re-
- defined.
-
-
- (*)BackSpace ERASE PREV
- (*)Tab INSERT CHAR
- (*)Enter INSERT CHAR
- (*)Space INSERT CHAR
-
- Home MOVE HOME
- End MOVE END
- Del ERASE CHAR
- PgUp PREV SCREEN
- PgDn NEXT SCREEN
- Up MOVE UP
- Down MOVE DOWN
- Left MOVE LEFT
- Right MOVE RIGHT
-
- Ctrl-Enter AUTO INDENT
-
-
-
-
-
-
-
-
-
-
-
-
-
-
-
-
-
-
-
-
-
-
-
-
-
- - 52 -
-
-
-
- A P P E N D I C E S
-
- A. Key Bindings
-
- 2. Standard/CUA
-
-
- F10 DO COMMAND
-
- F01 ALTHELP
- F02 BUFFER
- F03 FINDNEXT
- F06 CHANGE DIR
- F07 LEARN
- F08 REPEAT
-
- Shift-F01 HELP
- Shift-F03 FIND
- Ctrl-F06 OTHER WINDOW
- Alt-F03 REPLACE
- Alt-F04 EXIT
-
- Up MOVE UP
- Down MOVE DOWN
- Left MOVE LEFT
- Right MOVE RIGHT
- Home MOVE HOME
- End MOVE END
- Ctrl-Home MOVE TOP
- Ctrl-End MOVE BOTTOM
- Ctrl-Right MOVE WORD
- Ctrl-Left EXECUTE STDWREV
- Ctrl-Up PREV LINE
- PgUp PREV SCREEN
- Ctrl-Down NEXT LINE
- PgDn NEXT SCREEN
- Shift-Ctrl-Left SHIFT LEFT
- Shift-Ctrl-Right SHIFT RIGHT
- Ctrl-PgUp EXECUTE STDOTHUP
- Ctrl-PgDn EXECUTE STDOTHDN
-
- Del ERASE CHAR
- Ctrl-Backspace ERASE WORD
- Ctrl-Y ERASE LINE
- Shift-Ctrl-Y ERASE LINE
- Alt-Backspace RESTORE TEXT
-
- Shift-Del REMOVE TEXT
- Ctrl-Del WIPE TEXT
- Ctrl-Ins STORE TEXT
- Shift-Ins INSERT HERE
-
-
- - 53 -
-
-
-
- Shift-Ctrl-I INDENT 1
- Shift-Ctrl-U INDENT -1
- Ctrl-0 GOTO MARK
- Ctrl-B RECALL
- Ctrl-O OPEN LINE
- Ctrl-V QUOTE CHAR
- Ctrl-R REMEMBER
- Ctrl-W REFRESH SCREEN
-
- Alt-1 ONE WINDOW
- Alt-2 TWO WINDOWS
- Alt-A LIST ASCII
- Alt-C CAPITAL WORD
- Alt-D DRAW
- Alt-F FILL PARA
- Alt-G GET FILE
- Alt-I INCLUDE FILE
- Alt-J JUSTIFY PARA
- Alt-K DEFINE KEY
- Alt-L LOWER WORD
- Alt-M SET MARGINS
- Alt-N RENAME FILE
- Alt-P SET PINDENT
- Alt-Q QUIT
- Alt-R RULER
- Alt-S SELECT TEXT
- Alt-T TRANS CHAR
- Alt-U UPPER WORD
- Alt-V SET VIDEO
- Alt-W WRITE FILE
-
- Esc ABORT
- Ctrl-Enter AUTO INDENT
- Ins CHANGE MODE
- Shift-Ctrl-0 MARK
- Alt-Left LEFT LINE
- Alt-Center CENTER LINE
- Alt-Right RIGHT LINE
- Shift-Ctrl-P PRINT BUFFER
- Shift-Ctrl-Q SHOW PRINTER
- Shift-Ctrl-G SET SCOPE GLOBAL
- Shift-Ctrl-L SET SCOPE LOCAL
-
-
-
-
-
-
-
-
-
-
-
- - 54 -
-
-
-
- A P P E N D I C E S
-
- A. Key Bindings
-
- 3. WordStar
-
-
- Esc DO COMMAND
-
- F01 HELP
- F03 FINDNEXT
- F05 CHANGE MODE
- F06 CHANGE DIR
- F07 LEARN
- F08 REPEAT
- F11 STORE TEXT
-
- Ctrl-A EXECUTE WSTWREV
- Ctrl-B FILL PARA
- Ctrl-C NEXT SCREEN
- Ctrl-D MOVE RIGHT
- Ctrl-E MOVE UP
- Ctrl-F MOVE WORD
- Ctrl-G ERASE CHAR
- Ctrl-L FINDNEXT
- Ctrl-N OPEN LINE
- Ctrl-P QUOTE CHAR
- Ctrl-R PREV SCREEN
- Ctrl-S MOVE LEFT
- Ctrl-T ERASE WORD
- Ctrl-U RESTORE TEXT
- Ctrl-V CHANGE MODE
- Ctrl-W PREV LINE
- Ctrl-X MOVE DOWN
- Ctrl-Y ERASE LINE
- Ctrl-Z NEXT LINE
-
- Ctrl-K+B SELECT TEXT
- Ctrl-K+C INSERT HERE
- Ctrl-K+D GET FILE
- Ctrl-K+F RENAME FILE
- Ctrl-K+P PRINT BLOCK
- Ctrl-K+Q QUIT
- Ctrl-K+R INCLUDE FILE
- Ctrl-K+S WRITE FILE
- Ctrl-K+U SELECT TEXT
- Ctrl-K+Y REMOVE TEXT
- Ctrl-K+X EXIT
-
- Ctrl-Q+A REPLACE
- Ctrl-Q+C MOVE BOTTOM
-
-
- - 55 -
-
-
-
- Ctrl-Q+D MOVE END
- Ctrl-Q+F FIND
- Ctrl-Q+I LINE
- Ctrl-Q+P GOTO MARK
- Ctrl-Q+R MOVE TOP
- Ctrl-Q+S MOVE HOME
- Ctrl-Q+Y ERASE LINE
-
- Ctrl-O+C CENTER LINE
- Ctrl-O+L SET MARGINS
- Ctrl-O+R SET MARGINS
-
- Ctrl-Enter AUTO INDENT
-
- Alt-A LIST ASCII
- Alt-B BUFFER
- Alt-C CAPITAL WORD
- Alt-D DRAW
- Alt-H ALTHELP
- Alt-J JUSTIFY PARA
- Alt-K DEFINE KEY
- Alt-L LOWER WORD
- Alt-O OTHER WINDOW
- Alt-P SET PINDENT
- Alt-Q QUIT
- Alt-R REMEMBER
- Alt-S SET SCOPE
- Alt-T TRANS CHAR
- Alt-U UPPER WORD
- Alt-V SET VIDEO
- Alt-X ABORT
- Alt-1 ONE WINDOW
- Alt-2 TWO WINDOWS
-
- Home MOVE HOME
- End MOVE END
- Up MOVE UP
- Down MOVE DOWN
- Left MOVE LEFT
- Right MOVE RIGHT
- PgUp PREV SCREEN
- PgDn NEXT SCREEN
- Ins CHANGE MODE
- Del ERASE CHAR
- Ctrl-Left SHIFT LEFT
- Ctrl-Right SHIFT RIGHT
- Ctrl-PgUp EXECUTE WSTOTHUP
- Ctrl-PgDn EXECUTE WSTOTHDN
-
-
-
-
-
- - 56 -
-
-
-
- A P P E N D I C E S
-
- A. Key Bindings
-
- 4. Word Perfect
-
-
- Esc DO COMMAND
-
- F01 ABORT
- F02 FIND
- F03 ALTHELP
- F04 INDENT 1
- F05 GET FILE
- F07 QUIT
- F10 WRITE FILE
-
- Shift-F02 FINDNEXT
- Shift-F03 OTHER WINDOW
- Shift-F04 INDENT -1
- Shift-F06 CENTER LINE
- Shift-F08 SET MARGINS
- Shift-F10 INCLUDE FILE
-
- Ctrl-F01 DOS
- Ctrl-F10 LEARN
-
- Alt-F02 REPLACE
- Alt-F04 SELECT TEXT
- Alt-F06 RIGHT LINE
- Alt-F09 DRAW
- Alt-F10 EXECUTE
-
- Ctrl-Home LINE
- Ctrl-Left EXECUTE WPFWREV
- Ctrl-Right MOVE WORD
- Home+Left SHIFT LEFT
- Home+Right SHIFT RIGHT
- Home+Up MOVE TOP
- Home+Down MOVE BOTTOM
- Home+Home MOVE HOME
- End MOVE END
- Home+End MOVE END
-
- Ctrl-F03+C SET COLOR
- Ctrl-F03+K DEFINE KEY
- Ctrl-F03+R RULER
- Ctrl-F03+1 ONE WINDOW
- Ctrl-F03+2 TWO WINDOWS
-
- Ctrl-F04+1 REMOVE TEXT
-
-
- - 57 -
-
-
-
- Ctrl-F04+2 STORE TEXT
- Ctrl-F04+Del WIPE TEXT
- Ctrl-F04+R INSERT HERE
-
- Shift-F07+P PRINT BUFFER
- Shift-F07+B PRINT BLOCK
- Shift-F07+D PRINT DELETE
- Shift-F07+C PRINT CANCEL
- Shift-F07+S SHOW PRINTER
-
- Del ERASE CHAR
- Ctrl-Backspace ERASE WORD
- Ctrl-End ERASE LINE
- Alt-Backspace RESTORE TEXT
-
- Ctrl-Enter AUTO INDENT
- Ctrl-R REMEMBER
-
- Up MOVE UP
- Down MOVE DOWN
- Left MOVE LEFT
- Right MOVE RIGHT
- PgUp PREV SCREEN
- PgDn NEXT SCREEN
- Ins CHANGE MODE
- Ctrl-PgUp EXECUTE WPFOTHUP
- Ctrl-PgDn EXECUTE WPFOTHDN
-
- Alt-A LIST ASCII
- Alt-B BUFFER
- Alt-C CAPITAL WORD
- Alt-D CHANGE DIR
- Alt-F FILL PARA
- Alt-H HELP
- Alt-J JUSTIFY PARA
- Alt-K QUOTE CHAR
- Alt-L LOWER WORD
- Alt-P SET PINDENT
- Alt-Q QUIT
- Alt-R REPEAT
- Alt-S SET SCOPE
- Alt-T TRANS CHAR
- Alt-U UPPER WORD
- Alt-V SET VIDEO
- Alt-X EXIT
-
-
-
-
-
-
-
-
- - 58 -
-
-
-
- A P P E N D I C E S
-
- A. Key Bindings
-
- 5. Microsoft Quick
-
- Esc DO COMMAND
-
- F01 HELP
- F02 BUFFER
- F03 FINDNEXT
- F05 CHANGE MODE
- F06 CHANGE DIR
- F07 LEARN
- F08 REPEAT
-
- Alt-F+O GET FILE (Open)
- Alt-F+M INCLUDE FILE (Merge)
- Alt-F+S WRITE FILE (Save)
- Alt-F+A RENAME FILE (save As)
- Alt-F+P PRINT BUFFER (Print)
- Alt-F+D DOS
- Alt-F+X EXIT (eXit)
-
- Alt-E+S SELECT TEXT
- Alt-E+T REMOVE TEXT (cuT)
- Alt-E+C STORE TEXT (Copy)
- Alt-E+P INSERT HERE (Paste)
- Alt-E+E WIPE TEXT (Erase)
- Alt-S+F FIND (Find)
- Alt-S+R FINDNEXT (Repeat find)
- Alt-S+C REPLACE (Change)
-
- Ctrl-C ABORT
- Ctrl-L FINDNEXT
- Ctrl-P QUOTE CHAR
- Ctrl-T ERASE WORD
- Ctrl-U RESTORE TEXT
- Ctrl-V CHANGE MODE
- Ctrl-Y ERASE LINE
- Ctrl-B RECALL
- Ctrl-O OPEN LINE
- Ctrl-R REMEMBER
- Ctrl-W PREV LINE
- Ctrl-Z NEXT LINE
-
- Ctrl-Enter AUTO INDENT
-
- Alt-1 ONE WINDOW
- Alt-2 TWO WINDOWS
- Alt-A LIST ASCII
-
-
- - 59 -
-
-
-
- Alt-C CAPITAL WORD
- Alt-D DRAW
- Alt-H ALTHELP
- Alt-F FILL PARA
- Alt-J JUSTIFY PARA
- Alt-K DEFINE KEY
- Alt-L LOWER WORD
- Alt-M SET MARGINS
- Alt-O OTHER WINDOW
- Alt-P SET PINDENT
- Alt-Q QUIT
- Alt-T TRANS CHAR
- Alt-U UPPER WORD
- Alt-V SET VIDEO
- Alt-X EXECUTE
-
- Home MOVE HOME
- End MOVE END
- Up MOVE UP
- Down MOVE DOWN
- Left MOVE LEFT
- Right MOVE RIGHT
- PgUp PREV SCREEN
- PgDn NEXT SCREEN
- Ins CHANGE MODE
- Del ERASE CHAR
- Ctrl-Left EXECUTE QUIWREV
- Ctrl-Right MOVE WORD
- Ctrl-Home MOVE TOP
- Ctrl-End MOVE BOTTOM
- Shift-Ctrl-Left SHIFT LEFT
- Shift-Ctrl-Right SHIFT RIGHT
- Ctrl-PgUp EXECUTE QUIOTHUP
- Ctrl-PgDn EXECUTE QUIOTHDN
-
-
-
-
-
-
-
-
-
-
-
-
-
-
-
-
-
-
-
- - 60 -
-
-
-
- A P P E N D I C E S
-
- A. Key Bindings
-
- 6. Emacs
-
-
- Esc+Esc DO COMMAND
-
- F01 HELP
- F03 FINDNEXT
- F05 CHANGE MODE
- F06 CHANGE DIR
- F09 RESTORE TEXT
- F11 STORE TEXT
-
- Ctrl-A MOVE HOME
- Ctrl-B MOVE LEFT
- Ctrl-C DOS
- Ctrl-D ERASE CHAR
- Ctrl-E MOVE END
- Ctrl-F MOVE RIGHT
- Ctrl-G ABORT
- Ctrl-K ERASE LINE
- Ctrl-L REFRESH SCREEN
- Ctrl-N MOVE DOWN
- Ctrl-P MOVE UP
- Ctrl-S FIND
- Ctrl-T TRANS CHAR
- Ctrl-U REPEAT
- Ctrl-V NEXT SCREEN
- Ctrl-W REMOVE TEXT
- Ctrl-Y INSERT HERE
- Ctrl-Z EXIT
-
- Ctrl-X+( LEARN
- Ctrl-X+) REMEMBER
- Ctrl-X+1 ONE WINDOW
- Ctrl-X+2 TWO WINDOWS
- Ctrl-X+B BUFFER
- Ctrl-X+E EXECUTE
- Ctrl-X+N OTHER WINDOW
- Ctrl-X+P OTHER WINDOW
- Ctrl-X+Ctrl-C QUIT
- Ctrl-X+Ctrl-F RENAME FILE
- Ctrl-X+Ctrl-P PRINT BLOCK
- Ctrl-X+Ctrl-R INCLUDE FILE
- Ctrl-X+Ctrl-S WRITE FILE
- Ctrl-X+Ctrl-V GET FILE
-
- Esc+. SELECT TEXT
-
-
- - 61 -
-
-
-
- Esc+< MOVE TOP
- Esc+> MOVE BOTTOM
- Esc+B EXECUTE EMCWREV
- Esc+C CAPITAL WORD
- Esc+D ERASE WORD
- Esc+F MOVE WORD
- Esc+L LOWER WORD
- Esc+U UPPER WORD
- Esc+V PREV SCREEN
-
- Ctrl-Enter AUTO INDENT
-
- Alt-A LIST ASCII
- Alt-D DRAW
- Alt-F FILL PARA
- Alt-H ALTHELP
- Alt-J JUSTIFY PARA
- Alt-K DEFINE KEY
- Alt-M SET MARGINS
- Alt-P SET PINDENT
- Alt-Q QUIT
- Alt-R REPLACE
- Alt-S SET SCOPE
- Alt-V SET VIDEO
-
- Home MOVE HOME
- End MOVE END
- Up MOVE UP
- Down MOVE DOWN
- Left MOVE LEFT
- Right MOVE RIGHT
- PgUp PREV SCREEN
- PgDn NEXT SCREEN
- Ins CHANGE MODE
- Del ERASE CHAR
- Ctrl-Left SHIFT LEFT
- Ctrl-Right SHIFT RIGHT
- Ctrl-PgUp EXECUTE EMCOTHUP
- Ctrl-PgDn EXECUTE EMCOTHDN
-
-
-
-
-
-
-
-
-
-
-
-
-
-
- - 62 -
-
-
-
- A P P E N D I C E S
-
- B. The DOS Environment
-
- Most PC users are familiar with the DOS PATH command. A statement
- of the form
-
- PATH=C:\;C:\DOS\;C:\PEDIT
-
- in your AUTOEXEC file tells DOS where to look for programs and
- batch files. Unfortunately, the DOS environment is a mystery to
- most.
-
- Environment variables are defined using the SET command at the DOS
- prompt. The command "SET" by itself displays a list of all defined
- variables while "SET NAME=VALUE" defines a variable. Programs can
- read these environment variables and get access to the equivalence
- value. Adding a line such as:
-
- SET PEDIT=C:\PEDIT
-
- to your AUTOEXEC.BAT file lets pEDIT find its initialization and
- help files no matter what device/directory you are in. Note that
- only a device and directory are specified.
-
- Following is a sample AUTOEXEC.BAT file showing the DOS PATH and
- the PEDIT environment variable. Note that these items *must* be
- defined before entering a DOS shell such as HDM; if they were
- after "HDM" in this case, the statements would never be executed.
-
- PATH=C:\;C:\DOS;C:\WINDOWS;C:\PEDIT
- SET PEDIT=C:\PEDIT
- CD \HDM
- HDM
-
- DOS allocates only a relatively small amount of memory for the
- environment and it is possible to exceed this. The error is 'Out
- of environment space' while booting. If this happens and you have
- DOS 3.1 or higher, add the following line to your CONFIG.SYS file
- to reserve more space:
-
- SHELL=C:\DOS\COMMAND.COM C:\DOS /E:nnn /P
-
- Substitute your device and path in place of C:\DOS. For DOS 3.1,
- use /E:16 to reserve 16 paragraphs or 256 bytes. For DOS 3.2 or
- higher, specify /E:256.
-
- In DOS Version 2, unfortunately, there is no way to increase the
- environment space. You have no alternative here but to, for ex-
- ample, shorten the DOS PATH.
-
-
-
- - 63 -
-
-
-
- A P P E N D I C E S
-
- C. Supported Video Displays
-
- 1. MDA
-
- The Monochrome Display Adapter is the original text-only display.
- It supports only two 'colors' such as black and white or black and
- green. pEDIT+ can only run in text mode on this type of display.
-
-
- 2. HGA
-
- The Hercules Graphics Adapter provides monochrome graphics on a
- monochrome display. Unfortunately, the fast text display routines
- used by pEDIT do not support the standard 80x25 mode, so users
- with Hercules displays can run in text mode only.
-
-
- 3. CGA
-
- The Color Graphics Adapter was the first color display that
- supported graphics. The resolution is horrible and colors are
- limited to two palettes of 4 colors each in low-res (40 column)
- mode, and only 2 colors in high-res mode. pEDIT runs in hi-res
- 640x200 mode on a CGA monitor; the text resolution (8x8 cell) is
- horrible also. The extended characters above Ascii 127 are not
- available in CGA graphics mode.
-
-
- 4. EGA
-
- The Enhanced Graphics Adapter provides MUCH better graphics and
- text resolution than the CGA. Graphics mode displays 640x350 dots,
- and text uses a 8x14 cell. Sixteen colors are available on color
- displays. A minimum of 256k of EGA memory is required; some very
- old EGA cards have only 64k.
-
- An EGA display can also be attached to an IBM monochrome adapter.
- pEDIT PLUS supports this configuration, but with only 2 text
- colors possible. The only valid combination is black on white.
-
-
- 5. VGA
-
- The Video Graphics Array offers a slightly better resolution
- (640x480) than EGA. pEDIT PLUS runs a VGA display in EGA mode to
- be compatible with the standard 80x25 text mode.
-
- Sixteen colors are available on color displays. A VGA display can
- also be attached to an IBM monochrome adapter. pEDIT supports this
-
-
- - 64 -
-
-
-
- configuration as above with black on white again being the only
- valid color combination.
-
-
- 6. MCGA
-
- The MultiColor Graphics Array was supplied with some low-end PS/2
- models. It provides CGA modes plus the VGA 640x480 2-color mode.
- pEDIT can run the MCGA only in CGA 2 color mode; unfortunately,
- MCGA users will be stuck with the low resolution of this mode.
-
-
- 7. Other
-
- You should be able to run pEDIT PLUS in graphics mode on any
- display that supports a VGA-compatible mode. You may have to force
- your system into VGA mode before starting up pEDIT; refer to the
- manuals that came with your display and/or adapter card for more
- information.
-
-
-
-
-
-
-
-
-
-
-
-
-
-
-
-
-
-
-
-
-
-
-
-
-
-
-
-
-
-
-
-
-
-
- - 65 -
-
-
-
- A P P E N D I C E S
-
- D. Initialization File
-
- pEDIT requires an initialization file at startup. This file must
- either be located in the current directory or be available through
- translation of the DOS environment variable PEDIT. The default
- init file is named PEDIT.INI; pEDIT looks for this file unless you
- specify an alternate by including @XXX on the command line, where
- XXX = EMC, QUI, STD, WPF or WST.
-
- Five sample initialization files are included:
-
- STD Standard--pEDIT's own; now CUA-compliant with <F01>
- = Help, <Shift-Del> = cut, <Shift-Ins> = paste, etc.
-
- WST WordStar--the first PC word processor; many people
- know the WordStar keys and LOTS of software still
- uses these obscure key definitions
-
- WPF WordPerfect--still the top seller, complete with
- its finger-tangling assortment of meaningless Shift-,
- Ctrl- and Alt- keys
-
- QUI Quick--Microsoft's Quick Editor, used by the Quick
- Compilers and the DOS 5 Editor; an example is the
- combination <Alt-F+O> = Open file
-
- EMC Emacs--the famous UNIX programmer's editor; uses
- mnemonics, i.e. <Esc+F> = word forward, <Esc+B> =
- word back
-
- An initialization file is a text file containing any combination
- of the following commands: DEFINE_SHIFT(), DEFINE_KEY(), SET() and
- EXECUTE(). Note the underscore between words and the parentheses.
- The commands can be uppercase, lowercase or mixed. The editor
- ignores blank lines and treats anything after an exclamation point
- as a comment.
-
- Unlike other editors, pEDIT uses English key names. You don't have
- to try and remember what '@' and '#' stand for. pEDIT uses the
- names shown on the keys: Shift, Ctrl and Alt.
-
- DEFINE_SHIFT is used to define a shift or 'lead-in' key and tells
- pEDIT that the key will be the first key of a multi-key command.
- For example, DEFINE_SHIFT (Ctrl-Q) sets up Ctrl-Q as one of Word-
- Star's lead-in keys. The shift keys must be defined at the top of
- the init file before any key definitions that use that shift key.
-
- DEFINE_KEY defines a key. Obviously, no one would want to have to
- define each key every time they wanted to edit something, so these
-
-
- - 66 -
-
-
-
- bindings should be in the iniitialization file. The statement
- DEFINE_KEY (Get_File, Alt-G) binds the key Alt-G to the procedure
- GET FILE. A plus (+) sign between two key names indicates a two
- key command. For example, the statement DEFINE_KEY (Find, Ctrl-
- Q+F) defines WordStar's FIND key.
-
- SET is used to define the editing environment. If you wanted pEDIT
- to always come up in color using blue on a white background, you
- would include SET (COLOR, BLU, WHT) in the initialization file.
- This would be the same as entering the command "SET COLOR blu wht"
- from within pEDIT.
-
- EXECUTE is used to auto-execute a macro at startup time. If you
- wanted to execute a macro named LETTER every time you started
- pEDIT, for example, you would add EXECUTE (letter) to your INI
- file.
-
- Again, you don't have to use any of the initialization files
- supplied with the editor. You can set up any keyboard mapping you
- want.
-
-
- E. Help Files
-
- The Help File PEDIT.HLP is required if you want to use the HELP
- function. This file contains fixed 78-byte records. The editor
- uses random file access to read the help file so it must be made
- up of fixed-length records.
-
- You can customize the Help File as long as you keep the length of
- each record at exactly 78 bytes by 'padding' with spaces. You will
- need to limit each command's text to 19 lines (one screenful) of
- text. If you look at the file, you will see the first record for a
- command starts with two carets plus the command name in caps - for
- example "^^MOVE UP".
-
- The editor uses the optional files PEDIT.BTN and PEDIT.KEY for the
- ALTHELP command. When this command is invoked, pEDIT displays the
- contents of the these two files in BUTTON and KEYBOARD windows,
- respectively. pEDIT PLUS comes with five sample Keyboard Help
- Files corresponding to the five Initialization Files listed above.
- You can customize the Keyboard Help File any way you want.
-
-
-
-
-
-
-
-
-
-
-
- - 67 -
-
-
-
- A P P E N D I C E S
-
- F. Color Codes
-
-
- BLK Black
- BLU Blue
- GRN Green
- CYN Cyan
- RED Red
- MAG Magenta
- BRN Brown
- WHT White
- GRY Grey
- LBL Light Blue
- LGR Light Green
- LCY Light Cyan
- LRD Light Red (Pink)
- LMG Light Magenta
- YEL Yellow
- BWH Bright White
-
-
- The light colors are also called bright or intense. Only certain
- combinations are legal for VGA/EGA color displays. The foreground
- color can be any of the 16 listed above; the background, however,
- is limited to the normal (non-intense) colors.
-
-
-
-
-
-
-
-
-
-
-
-
-
-
-
-
-
-
-
-
-
-
-
-
-
-
- - 68 -
-
-
-
- A P P E N D I C E S
-
- G. Troubleshooting
-
-
- 1. pEDIT can't find the files it needs
-
- If you see the error "Initialization file not found" when starting
- pEDIT, there is a serious problem. pEDIT *MUST* be installed on
- your system for it to function properly. If pEDIT has indeed been
- installed, check your AUTOEXEC.BAT file to make sure the "SET
- PEDIT=" statement is being executed. The section titled 'The DOS
- Environment' has more information.
-
-
- 2. The screen is blank or garbage
-
- pEDIT cannot correctly identify your video display type. Adding
- the line "SET (DISPLAY, n)" to your PEDIT.INI file will force
- pEDIT to use the specified mode. Try text mode (n = 0) first; then
- try other values of n. See the SET DISPLAY command for a list of
- valid display numbers.
-
-
- 3. No mouse pointer at startup
-
- pEDIT could not detect a Microsoft compatible mouse driver. The
- mouse driver must be installed either at system startup by placing
- the statement "DEVICE=d:\path\MOUSE.SYS" in the file CONFIG.SYS,
- or from the DOS command line by executing the MOUSE program.
-
-
- 4. Mouse pointer disappears
-
- If this should happen, press any key or click the left mouse
- button to restore the pointer.
-
-
- 5. ButtonBar not graphical
-
- There are several possibilities: (1) you have a text-only display;
- (2) you are using a Hercules monochrome graphics adapter or (3)
- the program cannot find the ButtonBar image file "PEDIT.BAR".
-
-
- 6. ButtonBar trashed
-
- The most likely cause for this is having the wrong ButtonBar image
- file installed. pEDIT expects you to have one and only one display
- in use. If the image file is somehow lost, you can get it back
- from the distribution disk.
-
-
- - 69 -
-
-
-
- 7. Invalid drive or drive unavailable
-
- You have referenced a drive that doesn't exist or a floppy drive
- is not available, i.e. no diskette is loaded or the latch is open.
-
-
- 8. Garbage in printed documentation
-
- PEDIT.DOC uses the special characters above Ascii 127 for line and
- box drawing. A printer that supports the IBM Extended Character
- Set is required to print this document. Many printers including
- the HP LaserJet can print these characters but must be configured
- to do so; refer to your printer manual.
-
- If your printer cannot handle these special characters, use the
- new DRAW command to convert them to standard Ascii characters.
-
-
- 9. Blank pages in printed documentation
-
- The pEDIT documentation contains form feeds to facilitate print-
- ing. Unfortunately, many printers add their own form feeds to skip
- over page perforations. Please Refer to your printer manuals to
- see how to turn off the auto form feeding.
-
-
- 10. Can't use DOS command
-
- pEDIT "swaps" all text to disk before shelling to DOS. If there is
- not enough free disk space to hold the swap files, the function
- will be cancelled.
-
-
- 11. System hangs after using DOS command
-
- A good guess is that you executed a TSR (Terminate and Stay Res-
- ident) program when shelled to DOS. These TSRs must be loaded at
- startup time before you run any other programs.
-
-
- 12. Screen garbled after shelling DOS command
-
- For some unknown reason, DOS error messages such as "File not
- found" are NOT redirected to PED$$.TMP and can overwrite the pEDIT
- screen. Use the REFRESH SCREEN command to restore the screen.
-
-
- 13. Cursor disappears in graphics mode
-
- Because there is no hardware cursor in graphics mode, pEDIT must
- maintain its own. If the cursor state is lost, the cursor will
-
-
- - 70 -
-
-
-
- disappear. Sometimes the cursor can be restored by shelling to DOS
- and returning. If this doesn't work, you must quit and restart the
- program.
-
-
- 14. PRINT commands don't work
-
- PRINT only works in Registered versions of pEDIT PLUS. If you have
- registered, you must also have DOS 3.0 or higher and the DOS PRINT
- program must be installed. If you are still using the old DOS 2.x
- you should consider upgrading to DOS 5.0.
-
-
- 15. pEDIT "hangs" during a PRINT operation
-
- If the printer is off-line or out of paper when you issue the
- PRINT DELETE and PRINT CANCEL commands, pEDIT may appear to hang.
- If you put the printer back on-line, pEDIT will resume.
-
-
- 16. Garbage with EGA display adapter
-
- A minimum of 256k of EGA video memory is required for 16 colors;
- the original EGA adapter had only 64k. You will have to use pEDIT
- in text mode by including 'SET (DISPLAY, 0)' in your INI file.
-
-
-
-
-
-
-
-
-
-
-
-
-
-
-
-
-
-
-
-
-
-
-
-
-
-
-
-
- - 71 -
-
-
-
- A P P E N D I C E S
-
- H. RAMEDIT
-
-
- RAMEDIT is a new feature that lets you install auxillary pEDIT
- files on a RAM disk for faster operation. You should consider
- using RAMEDIT if you have a slow hard drive. You can disregard
- this section if you don't have software such as Microsoft's Smart-
- Drive that lets you emulate a disk drive in memory.
-
- RAMEDIT is a batch file that lets you install (or deinstall) the
- Initialization, Help, macro and other files to (from) a RAM drive.
- The executable is not copied. The pEDIT environment variable is
- also changed to point either to the RAM disk or the normal path.
-
- pEDIT PLUS will operate much faster this way because reading from
- memory is always faster than reading from a disk. You will see
- improvement in the time it takes to read the INI file, open the
- help file, and execute a macro. The DOS command in particular is
- much faster because the temp files can be written to the RAM disk.
-
- You may have to edit RAMEDIT.BAT for it to work correctly on
- your system. The supplied file is set up for the Standard config-
- uration and to use RAM Drive "D". Also, you will lose your updated
- PEDIT.INF file containing the last file you edited unless it is
- copied to your hard drive. You should consider having a shutdown
- batch file that does this and parks your hard drive heads. Please
- refer to the file RAMEDIT.BAT itself for more information.
-
- The syntax (with the file RAMEDIT.BAT in your DOS PATH) is:
-
- >RAMEDIT I (to install
- >RAMEDIT D (to deinstall
-
- Use the (D)einstall option if you need to free up space on your
- RAM drive before e.g. running Microsoft Windows.
-
- You can, if you wish, copy PEDIT.EXE to the RAM drive for even
- faster operation. It is strongly recommended that data files NOT
- be moved to the RAM drive for editing. They will load (and save)
- faster BUT you run the risk of losing your work if the computer
- hangs or you power off your system without copying the files to
- permanent storage.
-
-
-
-
-
-
-
-
-
- - 72 -
-
-
-
- I N D E X
-
-
- A
-
- ASCII 1, 12, 19, 21, 36, 47, 54, 56, 58, 59, 62, 64, 70
- AUTOEXEC 5, 6, 7, 46, 63, 69
-
- B
-
- BIOS 2, 43
- Batch File 4, 48, 63, 72
- Binary 1
- Boot 5, 6, 7, 43, 63
- Buffer Commands 27
- ButtonBar 1, 2, 3, 9, 13, 14, 17, 35, 40, 69
-
- C
-
- CGA 1, 3, 13, 37, 38, 64, 65
- COMMAND Buffer 1, 12, 27, 35
- COMMAND.COM 8, 63
- CUA 2, 43, 53, 66
- Click (Mouse) 2, 12, 13, 15, 16, 17, 25, 27, 29, 39, 45, 69
- Color 1, 3, 13, 37, 38, 50, 57, 64, 65, 67, 68
- Command Mode 12, 14, 35
- Commands ABORT 13, 23, 25, 27, 35, 36, 37, 39, 45
- Commands ALTHELP 12, 39
- Commands AUTO INDENT 20
- Commands BUFFER 14, 16, 27, 35, 46
- Commands CAPITAL WORD 21
- Commands CENTER LINE 20
- Commands CHANGE DIR 27
- Commands CHANGE MODE 27
- Commands DEFINE KEY 36
- Commands DEFINE SHIFT 36
- Commands DO BUTTON 35
- Commands DO COMMAND 12, 14, 23, 35, 36, 42, 50
- Commands DOS 14, 39, 44, 48, 50
- Commands DRAW 14, 36, 45
- Commands ERASE CHAR 13, 22
- Commands ERASE LINE 22
- Commands ERASE PREV 13, 22
- Commands ERASE WORD 22
- Commands EXECUTE 33, 34, 41
- Commands EXIT 39, 40, 44
- Commands FILL PARA 14, 19
- Commands FIND 14, 21, 23, 24, 27, 35, 38, 49
- Commands FINDNEXT 14, 23, 27, 35
- Commands GET FILE 14, 25
- Commands GOTO MARK 28
- Commands HELP 10, 12, 14, 16, 35, 39
-
-
-
- Commands INCLUDE FILE 25
- Commands INDENT 19, 20, 38, 46
- Commands INSERT CHAR 19, 25
- Commands INSERT HERE 14, 32
- Commands JUSTIFY PARA 14, 19
- Commands LEARN 33
- Commands LEFT LINE 20
- Commands LINE 19, 20, 22, 28, 29, 38
- Commands LIST ASCII 21, 36
- Commands LIST KEYS 12, 36
- Commands LOWER WORD 21
- Commands MARK 27, 28
- Commands MOVE ABSOLUTE 17
- Commands MOVE BOTTOM 17
- Commands MOVE DOWN 18, 35, 37, 45
- Commands MOVE END 13, 17, 37, 45
- Commands MOVE HOME 13, 17, 37, 45
- Commands MOVE LEFT 13, 18, 37, 45
- Commands MOVE RIGHT 13, 18, 37, 45
- Commands MOVE TOP 17
- Commands MOVE UP 13, 17, 35, 37, 45
- Commands MOVE WORD 18, 27
- Commands NEXT LINE 29
- Commands NEXT SCREEN 30
- Commands ONE WINDOW 29
- Commands OPEN LINE 19
- Commands OTHER WINDOW 29
- Commands PREV LINE 29
- Commands PREV SCREEN 29
- Commands PRINT 38, 39, 44, 46
- Commands QUIT 14, 40
- Commands QUOTE CHAR 21
- Commands RECALL 35
- Commands REFRESH SCREEN 35
- Commands REMEMBER 33
- Commands REMOVE TEXT 14, 22, 31
- Commands RENAME FILE 25, 26, 50
- Commands REPEAT 33, 35, 37
- Commands REPLACE 14, 23, 27, 35, 38
- Commands RESTORE TEXT 22
- Commands RIGHT LINE 20
- Commands RULER 40
- Commands SAVE MACRO 33, 41
- Commands SELECT TEXT 31
- Commands SET AUTOSAVE 37
- Commands SET COLOR 37
- Commands SET CURSOR 37
- Commands SET DISPLAY 37
- Commands SET LINES 38
- Commands SET MARGINS 12, 19, 20, 38
- Commands SET PINDENT 19, 38
- Commands SET SCOPE 23, 38
-
-
-
- Commands SET VIDEO 38
- Commands SHIFT LEFT 14, 30
- Commands SHIFT RIGHT 14, 30
- Commands SHOW BUFFER 14, 27
- Commands SHOW KEY 36
- Commands SHOW PRINTER 39, 46
- Commands STORE TEXT 22, 31
- Commands TRANS CHAR 21
- Commands TRIM BUFFER 27
- Commands TWO WINDOWS 29
- Commands UPPER WORD 21
- Commands WIPE TEXT 31
- Commands WRITE FILE 12, 14, 25, 37
- Configuration 1, 2, 3, 4, 5, 8, 12, 41, 42, 43, 50, 52, 64
- CONFIG.SYS 63, 69
- Copyright 51
- Cursor 15, 16, 17, 37
- Cursor Movement 17
- Cut and Paste 31
-
- D
-
- DOS Buffer 1, 39, 48, 49
- DOS PATH 5, 6, 8, 63, 72
- Disk Macro 4, 33, 34, 41, 42, 48
- Diskette 3, 5, 6, 50, 70
- Distribution 3, 5, 6, 7, 69
- Double Click (Mouse) 2, 15, 25, 27, 39
- Drag (Mouse) 2, 15, 31
- Drawing 1, 14, 36, 37, 45, 70
-
- E
-
- EGA 1, 3, 4, 10, 13, 20, 37, 38, 48, 64, 68, 72
- EMACS 1, 3, 4, 5, 8, 61, 66
- EMC 3, 8, 41, 62, 66
- Environment 1, 5, 6, 8, 63, 66, 67, 69, 72
-
- F
-
- File Commands 25
- Floppy 1, 5, 6, 8, 70
-
- G
-
- Global Scope 1, 9, 10, 23, 38, 54
-
- H
-
- HDM 4, 63
- Hard Disk 6, 7
- Hard Drive 2, 5, 6, 8, 72
-
-
-
- Help File 3, 4, 5, 39, 63, 67, 72
- Hercules 1, 64, 69
-
- I
-
- INSTALL 3, 4, 5, 6, 7, 50
- Initialization file 4, 10, 35, 36, 38, 50, 66, 67, 69
-
- K
-
- KEYRATE 4, 5, 6, 7
- Key Macro 33, 34, 41
- Keyboard Help File 4, 67
-
- L
-
- Line and Box Drawing 1, 45
- Local Scope 10, 23, 38, 54
-
- M
-
- MCGA 65
- MS Quick 5
- Macro 4, 33, 34, 41, 42, 47, 48, 49, 67, 72
- Memory 1, 2, 5, 10, 17, 25, 31, 44, 46, 50, 63, 72
- Miscellaneous Commands 35
- Mouse 1, 2, 12, 13, 15, 16, 17, 25, 29, 31, 33, 35, 39, 44, 45, 69
- Mouse Button 15, 25, 33, 39
-
- P
-
- PATH 5, 6, 7, 8, 33, 39, 40, 41, 44, 63, 72
- PED$$$n.TMP 44
- PED$$.PRN 47
- PED$$.TMP 48, 70
- PEDIT PATH 8, 33, 39, 40, 41, 44
- PEDIT.BAR 69
- PEDIT.BTN 3, 8, 40, 67
- PEDIT.DOC 3, 70
- PEDIT.EXE 3, 8, 72
- PEDIT.HLP 3, 8, 39, 67
- PEDIT.INI 5, 8, 50, 66, 69
- PEDIT.KEY 5, 8, 40, 67
- PEDIT.SHR 3
- Pointer (Mouse) 15, 16, 17, 31, 69
- Print Queue 39, 46
- Printing 39, 46
- Prompting Mode 12
-
- Q
-
- QUI 3, 8, 14, 40, 41, 54, 55, 56, 57, 58, 60, 61, 62, 66
-
-
-
- R
-
- Reformat Paragraph 14
- Register 3, 4, 5, 17, 39, 46, 51, 71
- Registration 51
- Repaginate 47
-
- S
-
- STAYDOWN 4, 5, 6, 7
- STD 2, 3, 8, 41, 42, 43, 53, 66
- Scope 10, 23, 38, 54, 56, 58, 62
- Scroll 2, 10, 15, 16, 17, 18, 29, 30, 31, 35, 38, 41, 42
- Searching 12, 23
- Shareware 1, 4, 46, 51
- Shell 1, 14, 39, 44, 46, 48, 50, 63, 70, 71
- Special Char 21
- Standard 2, 3, 4, 5, 8, 12
-
- T
-
- TSR 43, 44, 46, 70
- Text Deletion 22
- Text Manipulation 19
- Troubleshooting 69
- Tutorial 3, 5
-
- U
-
- Undo 22, 31
-
- V
-
- VGA 1, 3, 10, 13, 37, 38, 64, 65, 68
- Video Display 38, 64, 69
-
- W
-
- WPF 3, 8, 41, 57, 58, 66
- WST 3, 8, 41, 55, 56, 66
- Window Commands 29
- WordPerfect 1, 4, 43
- Wordstar 1, 3, 4, 5, 8, 35, 51, 55, 66, 67
-